Skip to main content
Glama

KEVAREMESH Free Agent API Gateway

Get original reviewed input schema for a KEVAREMESH owned API

kevaremesh_get_owned_input_contract
Read-onlyIdempotent

Free lookup of a catalog-listed first-party API's original input contract; preview is only available for locally approved algorithms. This is not a paid API execution contract or merchant authorization.

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": {
      "slug": "<slug>"
    },
    "name": "kevaremesh_get_owned_input_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is supplied. The description adds that the lookup is free and preview eligibility depends on local approval, but it does not explain auth requirements, response contents, or caching behavior. Additional context is useful but limited.

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

Conciseness4/5

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

The description is concise and front-loads the free lookup purpose. The second sentence usefully scopes out paid execution and merchant authorization. No filler is present, though naming the slug as the API identifier would strengthen the structure.

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

Completeness3/5

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

With one required parameter, no output schema, and simple annotations, the definition covers the basic contract. However, it does not explain what the returned 'original input contract' contains or clarify the locally approved algorithms condition. It is adequate but leaves gaps relevant to invoking the tool confidently.

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 description coverage is 0% for the single slug parameter, so the description must carry parameter meaning. It implies that the lookup targets a catalog-listed first-party API but never explicitly says the slug identifies that API or gives format expectations. The schema pattern supplies constraints, but the description adds minimal semantic clarity.

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

Purpose3/5

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

The description says it is a free lookup of a catalog-listed first-party API's original input contract and distinguishes it from paid execution or merchant authorization. However, it does not use a crisp verb+resource framing and only implicitly differentiates from siblings like kevaremesh_preview_owned_api and kevaremesh_find_owned_api.

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 only explicit condition is that preview is available for locally approved algorithms. There is no direct guidance on when to use this tool versus sibling lookup, preview, quote, or retrieval tools. The agent has to infer that this retrieves input schema metadata rather than executing or authorizing anything.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources