Love Calculator SkillLove Calculator Skill

OnlineCredit Usage:1 per callTool:LoveCalculatorSkill

The tool

Add a love-compatibility score to your agent or app. Call it as an MCP tool to return a fun match percentage for any two names.

Once your client is connected to the VerveKit MCP server, this appears in its tool list as LoveCalculatorSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.

Tool call
{
  "name": "LoveCalculatorSkill",
  "arguments": {
    "name1": "John",
    "name2": "Jane"
  }
}

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about John in the terms this source covers is enough for it to reach for LoveCalculatorSkill on its own.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.

Client config
{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervekit.com/v1/mcp

Per-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.

ArgumentTypeExampleDescription
name1RequiredstringJohnThe first name to calculate love compatibility
name2RequiredstringJaneThe second name to calculate love compatibility

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "name1": "Jane",
    "name2": "John",
    "lovePercentage": "62%",
    "response": "You have good chemistry. Keep getting to know each other and see where it leads.",
    "additionalText": "The love percentage between Jane and John is 62%."
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
name1stringJaneThe first name provided for compatibility calculation
name2stringJohnThe second name provided for compatibility calculation
lovePercentagestring62%Calculated love compatibility percentage between two names
responsePremiumstringYou have good chemistry. Keep getting to know each other and see where it leads.Detailed compatibility analysis and advice for the couple
additionalTextstringThe love percentage between Jane and John is 62%.Additional information and summary about love percentage

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This skill isn't part of VerveKit. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use Love Calculator Skill

Set up Love Calculator Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →

Frequently asked questions

Do I have to tell the agent to use LoveCalculatorSkill?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?