Skip to main content
Glama

Find tools, including unloaded ones

explore_tools
Read-only

Find TrueScrape tools, including those this connection did not load, with cost and input schema. With no arguments, lists platforms and tool counts. Run what you find with call_tool. Free.

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

Input Schema

NameRequiredDescriptionDefault
queryNoWords that must all appear in the tool name or description.
platformNoA platform name, as listed with no arguments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish that this is a read-only lookup, and the description adds useful behavioral context: results include cost and input schema, the tool is free, and discovered tools are run via call_tool. It does not cover result limits or pagination, which keeps it from a 5.

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 short, front-loaded, and wastes no space. The no-argument behavior, execution pointer, and cost note are all delivered in a few efficient sentences.

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 two-parameter read-only discovery tool with no output schema, the description is complete enough: it says what can be searched, what results include, what no arguments returns, and how to execute a found tool.

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%, so both query and platform are already fully documented. The description adds the useful no-argument behavior and mentions platform listing, but does not add much parameter semantics 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 states a specific verb and resource: find TrueScrape tools, including unloaded ones, with cost and input schema. It clearly distinguishes itself from actual platform tools and from call_tool by positioning this as discovery and call_tool as execution.

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 gives clear usage context, including the no-argument behavior that lists platforms and tool counts. It also explicitly routes execution to call_tool, though it does not state when not to use explore_tools versus using an already-known sibling directly.

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.