Skip to main content
Glama
agentisend

agentisend

List more tools

list_more_tools
Idempotent

Reveals server tools omitted from the default tools/list response and adds them to this connection for later use. Filter by category to expose only that area.

Instructions

Purpose: see the rest of this server's tools when tools/list only showed the default set, and add them to tools/list for this connection. Filter by category if you already know the area; only that category is added. NOT for: calling a tool. Once your client re-reads tools/list, call the new tools like any other. Not a second permission check. Returns: data, has_more (always false), and next_cursor (always null). Each row has name, title, description, category and required_scopes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_more_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOnly tools in this area. Omit for the full extra list.
idempotency_keyNoYour own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect.

Output Schema

NameRequiredDescriptionDefault
dataNoThis page of rows.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
has_moreNoTrue when another page follows.
next_cursorNoPass back as cursor for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, and the description supplies the reason — the call mutates connection-level tool visibility — which is exactly the context annotations can't convey. It also discloses the odd return shape (has_more always false, next_cursor always null) and the per-row fields including required_scopes. Minor gap: it doesn't say whether the added tools persist for the session or can be reverted.

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?

Front-loaded labeled structure (Purpose / NOT for / Returns) makes it scannable with no filler sentences. Slightly dense, but every line carries actionable information; nothing is repeated from the schema except the return field list, which is cheap and useful.

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

Completeness5/5

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

For a tool that mutates connection state, the description covers trigger condition, exclusions, follow-up action, filtering semantics, and return shape. With an output schema and full annotation set already present, nothing an agent needs to invoke it correctly is missing.

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 schema already documents both parameters and the enum values, giving a baseline of 3. The description goes beyond that by explaining the behavioral consequence of filtering — only the chosen category is added, implying repeated calls for other areas.

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+resource with its exact effect: surface the remaining server tools that tools/list omitted and add them to tools/list for this connection. The optional category filter and its consequence ('only that category is added') are spelled out, so it's distinguishable from the list_* siblings that enumerate data rather than tools.

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

Usage Guidelines5/5

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

Explicit when-to-use ('when tools/list only showed the default set'), plus a 'NOT for' block ruling out using it to call tools and ruling out treating it as a permission check. It also gives the follow-up step ('once your client re-reads tools/list, call the new tools like any other') and when to narrow by category.

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