Skip to main content
Glama

Look up the Casama API

get_api_operation
Read-only

Find Casama HTTP API operations by operationId, METHOD /path, or keywords, then view their parameters, request body, and responses as types.

Instructions

Find operations in the Casama HTTP API (OpenAPI 3.1) and show their parameters, request body and responses as types. Query by operationId ("createBot"), "METHOD /path" ("POST /v1/conversations/{id}/messages", concrete ids work too) or keywords ("cancel run").

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": {
      "query": "<query>"
    },
    "name": "get_api_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and a closed-world scope, so the safety profile is covered. The description usefully adds the return shape (parameters, body, responses as types) and the fact that concrete path ids are accepted in lieu of templates, but it is silent on matching ambiguity, ranking, or what happens when several operations match.

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?

A single, front-loaded sentence with no filler; the verb and resource come first and the query grammar follows. It is dense but every clause carries information, and example payloads in quotes aid scanning.

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?

For a two-parameter, read-only lookup with no output schema, the description covers purpose, query syntax and the shape of the returned type information. The only real omission is any mention of the 'limit' cap and result ordering, which an agent would need before relying on truncation behavior.

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%, so the description carries the whole burden. It compensates well for 'query' by spelling out the accepted formats, but the 'limit' parameter (1–10, defaulting implicitly) is never mentioned in either the schema or the description, leaving one of two parameters unexplained.

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?

States a specific verb and resource — find operations in the Casama HTTP API (OpenAPI 3.1) — and adds what is returned: parameters, request body and responses as types. That is enough for an agent to tell it apart from the documentation siblings, though no sibling is named and the distinction is only implied by the API-versus-docs framing.

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?

The three accepted query forms (operationId, "METHOD /path", free keywords) give clear guidance on how to invoke it, and concrete id substitution is noted as working. There is no explicit when-not or reference to the doc-reading siblings, so the alternative-selection guidance is inferred rather than stated.

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