Graph Paper

Search the help

lookup_help

Read-only

Needs sign-in: Search Graph Paper's product help — tips, commands, settings, and a product overview — for how the APPLICATION works. Consult it BEFORE answering any "how do I…" or "can Graph Paper do…" question rather than guessing from priors. Each match carries a kind and a title; attribute your answer using them. An explicit no-match result means the feature may not exist — say so plainly; never invent a menu, gesture, setting, or UI affordance.

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": "lookup_help"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	A product-feature question or keywords to search the help index for.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description goes beyond the read-only annotation by detailing the behavioral protocol: 'Each match carries a kind and a title; attribute your answer using them.' It also provides critical instructions on handling negative search results.

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?

Although long, the description is extremely efficient. Every sentence is necessary, detailing scope, usage protocol, output handling, and failure handling, justifying the necessary verbosity.

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?

The definition is exceptionally complete, addressing not just how to call the tool (query), but also how to correctly interpret both positive and negative results within the context of answering a user question.

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?

The input schema coverage is 100%, meaning the schema already clearly defines the `query` parameter. The description reinforces the context but adds no novel semantic meaning 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 purpose is highly specific, stating it searches 'Graph Paper's product help — tips, commands, settings, and a product overview.' This clearly defines the resource and scope.

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?

It provides explicit guidance on when to use the tool: 'Consult it BEFORE answering any "how do I…" or "can Graph Paper do…" question rather than guessing from priors.' It also specifies how to interpret a 'no-match result.'

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

All Graph Paper tools Inspect

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

Need Help?