Skip to main content
Glama

Oran Analiz Bot

Sonucun devamı

get_more
Read-only

Büyük bir araç sonucunun ⋯ ile işaretli bölümünü getirir. resultId, path ve offset işaretteki gibi verilir.

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": {
      "resultId": "<resultId>",
      "path": "<path>"
    },
    "name": "get_more"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesİşaretteki path, ör. ["matches"] ya da ["groups", 3].
offsetNoİşaretteki offset (liste/metinde kaldığı yer).
resultIdYesSayfalanan sonucun resultId'si.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds the genuinely useful behavioral fact that this is a continuation fetch tied to marker metadata, but says nothing about resultId lifetime, whether retrieval is idempotent, or what happens on a stale offset.

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?

Two short sentences with no filler; the purpose comes first and the parameter-provenance rule second. Nothing is redundant with the title or the schema.

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 three-parameter, fully documented, non-destructive continuation tool with no output schema, the description covers what an agent needs to decide and invoke. The remaining gap is minor: it does not say what the returned fragment looks like or how the agent knows it has reached the end.

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 coverage is 100%, so the baseline is 3. The description exceeds it by telling the agent the parameters are taken verbatim 'as in the marker', which is a non-obvious constraint — the agent should copy them from the truncation notice instead of synthesizing them. That meaning is not present in the schema property descriptions.

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 names a specific action and resource: retrieving the portion of a large tool result that was elided with a '⋯' marker. That is far more specific than the bare name 'get_more', and no sibling in the catalog does continuation/pagination, so confusion risk is low. It stops short of 5 only because it doesn't state the relationship to the producing tool by name.

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?

It conveys the trigger condition implicitly but clearly: when a result is shown truncated with '⋯', call this with the marker's resultId, path and offset. That is actionable invocation guidance rather than mere context. There is no explicit 'when not to use' statement or named alternative, which keeps it out of 5 territory.

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