Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

tes_resource_detail

Fetch Tes teaching resource details by numeric ID, including title, subject, age range, type, author, price, rating, licence, attachment metadata, and recent reviews.

Instructions

Get a Tes teaching resource. Returns detail for one teaching resource by its numeric id (the id field returned by tes-resource-search). Descriptive facts (title, subject, age range, resource type, author, price, rating, licence label), a per-file attachment list (file type, size, and a preview thumbnail -- metadata only), and the most recent page of reviews are returned -- not the downloadable resource file itself.

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.17.5Sep 26, 2026
- addedInput schema / properties / country / enum
```
Added value: +[
+  "GB",
+  "US",
+  "AU",
+  "IE",
+  "CA",
+  "NZ",
+  "UN"
+]
```
Addedv1.16.2Sep 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it enumerates the returned payload (facts, per-file attachment metadata, recent reviews page) and explicitly bounds behavior by stating it returns 'not the downloadable resource file itself'. It does not mention auth/permission needs or rate limits, but for a read-only detail fetch that is a minor gap.

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?

The purpose is front-loaded in the first sentence, followed by return-value detail. It is dense and somewhat run-on with stacked parentheticals, but essentially every clause adds actionable information (what is returned, id source, and the downloadable-file exclusion).

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?

With no output schema, the description compensates by describing the return payload in detail, including what is excluded. It is nearly complete for a 2-param read tool; only the country/currency param and any auth requirement are unaddressed, but the schema covers the former.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real value by clarifying that the id is numeric and originates from tes-resource-search's id field. The optional 'country' param (storefront/currency) is left to the schema, which documents it.

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+resource ('Get a Tes teaching resource') and defines the scope precisely as a single-resource detail lookup by numeric id. This clearly distinguishes it from siblings like tes_resource_search and tes_resource_shop, which are search/browse operations.

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?

The description tells the agent where the required id comes from ('the id field returned by tes-resource-search'), giving clear context for when to reach for this tool after a search. It does not, however, name explicit alternatives or state when-not-to-use conditions beyond the search linkage.

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

Deploy Server