Skip to main content
Glama
Sign In

Kareverse

by com.kareverse
OverviewDiscussionsAdmin

Get service details

get_service
Read-onlyIdempotent

Full details of one Kareverse service by id (from search_services): what is included and not included, price options, notice needed, FAQs and how to book.

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": {
      "id": "<id>"
    },
    "name": "get_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesService id, e.g. 'hospital-accompaniment'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered without prose. The description adds value beyond that by previewing the payload: inclusions/exclusions, price options, notice requirements, FAQs, and booking mechanics, telling the agent what a successful call yields.

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?

A single front-loaded sentence with the primary identity and source of the id first, then the returned sections. Every clause carries information; nothing is padded or redundant.

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 one required parameter, full schema coverage, and no output schema, the description usefully enumerates the return contents so the agent knows what questions this tool can answer. Missing only edge-case behavior (unknown id, error shape), which is minor for a simple read.

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

Parameters3/5

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

Schema coverage is 100% and the only parameter already has a format example ('hospital-accompaniment'). The description's contribution is provenance for the id (obtained from search_services), which is modest but genuinely additive over the schema text.

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

Purpose4/5

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

The description gives a specific verb and resource ("Full details of one Kareverse service by id") and scopes it to a single record, which distinguishes it from the list-style sibling search_services. It stops short of an explicit contrast statement, but the singular/plural split is obvious from the phrasing.

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

Usage Guidelines3/5

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

The parenthetical "(from search_services)" implies the intended workflow: find an id via search, then fetch details here. There is no explicit when-not guidance, no prerequisite statement, and no note about what to do with an invalid or unknown id.

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

All Kareverse toolsInspect
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.

Resources