Skip to main content
Glama
Sign In

TrueScrape

by io.github.TrueScrape
OverviewDiscussionsAdmin

Run a data tool found with explore_tools

call_tool
Read-only

Run a data tool by name, loaded or not, at that tool's own price. Monitor and watch tools are called directly.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTool name from explore_tools.
argumentsNoThe arguments that tool's input schema takes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds meaningful behavior: the target tool's own price is charged, tools may be loaded or not, and monitor/watch tools are invoked directly. It still omits error behavior, auth requirements, and whether the target tool's own side effects apply.

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?

Two sentences, front-loaded with the action and scope. The second sentence is terse but earns its place by excluding monitor/watch tools; overall it is efficient, though the fragment style leaves some ambiguity.

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?

The description covers cost, loading, and exclusions, and the schema documents the two parameters. However, for a generic dispatcher with no output schema, it does not describe what is returned or how failures from the target tool surface, leaving gaps an agent may need.

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 coverage is 100% and both parameters are documented in the schema, including the nested arguments object. The description adds only the 'by name' framing and no further syntax, validation, or nested-argument guidance, so baseline 3 is appropriate.

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: 'Run a data tool by name, loaded or not.' It ties the tool name back to explore_tools and explicitly excludes monitor/watch tools, though it does not fully explain its relationship to the many directly-named data tool siblings.

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

Usage Guidelines3/5

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

Provides partial routing: use names from explore_tools, and do not use call_tool for monitor/watch tools. It does not clarify when to call this dispatcher versus a directly exposed data tool, nor how to decide between loaded and unloaded tools beyond the phrase 'loaded or not.'

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

All TrueScrape 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