Kareverse

Request a callback from Kareverse

submit_enquiry

Send an enquiry so the Kareverse team calls or WhatsApps the family back. Only use this after the person has explicitly agreed to be contacted and has given their own name and phone number; set consent to true to confirm. Do not use it for emergencies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "phone": "<phone>",
      "consent": "<consent>"
    },
    "name": "submit_enquiry"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Name of the person Kareverse should contact.
`email`	No	Optional email address.
`phone`	Yes	Their phone or WhatsApp number, with country code (e.g. +91 98765 43210 or +1 415 555 0100).
`consent`	Yes	True only if the person agreed that Kareverse may contact them about this enquiry.
`message`	No	Short background, in the person's words.
`parent_area`	No	Where the parent lives in Bangalore.
`service_interest`	No	What they need, e.g. 'Care Plan', 'Hospital accompaniment', 'Night caretaker'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare it is a non-destructive, non-idempotent, open-world write. The description adds behavior the annotations cannot express: the consent gate, the human follow-up via phone or WhatsApp, and the emergency exclusion. It omits rate limits or duplicate-enquiry handling, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the action and outcome, then the precondition, then the exclusion. No filler or restated title text; every sentence constrains behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With all 7 parameters documented in the schema and no output schema to explain, the description covers the remaining gaps: consent authorization, outbound-contact implication, and the emergency exclusion. Minor omissions such as expected response time or whether repeat submissions create duplicate enquiries are not fatal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns the bump by clarifying that consent must be set to true to confirm and that the name and phone must belong to the person being contacted, which sharpens the semantics of the two required fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('send an enquiry') plus the concrete outcome ('so the Kareverse team calls or WhatsApps the family back'). This is clearly distinguishable from the read-only siblings (get_care_plan, search_services), since it is the only outbound-contact action described.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ('only use this after the person has explicitly agreed to be contacted and has given their own name and phone number') and an explicit exclusion ('do not use it for emergencies'). It does not name a sibling alternative, but no sibling performs this action, so nothing essential is left ambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Kareverse tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.