Skip to main content
Glama
Sign In

ai-agent-scratchpad

by io.github.lazymac2x
OverviewDiscussionsAdmin

scratchpad_list

세션의 모든 키 목록을 반환합니다. 선택적 prefix 필터링 지원.

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": {
      "session_id": "<session_id>"
    },
    "name": "scratchpad_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo최대 반환 수 (기본 100, 최대 500)
prefixNo키 prefix 필터 (선택사항)
session_idYes세션 식별자

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

There are no annotations, so the description must disclose behavioral traits. It conveys that the operation lists keys and supports prefix filtering, implying read-only behavior, but does not explicitly state non-mutating nature, ordering, or pagination semantics beyond the schema's limit parameter.

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?

The description is a single, front-loaded sentence in Korean that states the primary purpose first, followed by the optional capability. Every word earns its place with no repetition or filler.

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?

Given the simplicity of the tool and 100% schema coverage, the description is minimally adequate, but it omits any mention of the required session_id or the limit parameter, relying entirely on the schema. It also lacks comparative context with sibling tools, which is needed for a complete picture.

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 100%, so the baseline is 3. The description only mentions prefix filtering, which is already documented in the schema. It adds no extra meaning for session_id or limit beyond what the schema provides.

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?

The description clearly states the tool returns the list of all keys in the session and supports optional prefix filtering. This specific verb+resource combination distinguishes it from sibling tools like scratchpad_read or scratchpad_write.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It only describes what it does, without mentioning exclusions or suggesting when to prefer this over scratchpad_read or other sibling tools.

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

All ai-agent-scratchpad 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