Crawlora MCP

tes_resource_detail

Read-only

Fetch a Tes teaching resource by ID with subject, age range, type, author, price, rating, and recent reviews. Use tes_resource_search to find resources or tes_resource_shop for the seller's store.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Tes resource id
`country`	No	Storefront market for pricing/currency. Documented values: GB, US, AU, IE, CA, NZ, UN.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026
- addedInput schema / properties / country / description
```
Added value: +"Storefront market for pricing/currency. Documented values: GB, US, AU, IE, CA, NZ, UN."
```
- addedInput schema / properties / id / description
```
Added value: +"Tes resource id"
```
First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds the returnable field list, which is useful context, but discloses nothing about auth needs, rate limits, or pricing/currency behavior for the country parameter. With annotations carrying the safety burden, a 3 is appropriate.

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?

Two sentences with zero waste: the action is front-loaded and the routing guidance follows. The field enumeration is dense but directly useful, and nothing is redundant.

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

Completeness4/5

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

Output schema exists, so return values needn't be described (though the description does so anyway), and annotations cover safety. Purpose, routing, and parameters are all sufficiently covered; the only minor omission is any behavioral note on the country parameter's effect on pricing/currency, which the schema already handles.

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 both parameters (id and country) are already documented, including the country enum-like value list. The description only reinforces 'by ID' and adds no syntax or format detail beyond the schema, so the baseline 3 is correct when the schema does the heavy lifting.

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 ('Fetch') and resource ('Tes teaching resource by ID'), and enumerates the returned fields (subject, age range, type, author, price, rating, recent reviews). It names the two siblings it is distinct from, so an agent can route without opening any schema.

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?

Explicitly routes to alternatives: 'Use tes_resource_search to find resources or tes_resource_shop for the seller's store.' This tells the agent when this detail-by-ID tool applies versus discovery and seller-store tools, matching the strongest routing guidance in the calibration set.

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

All Crawlora MCP 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?