Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tes_resource_detail

Retrieve detailed metadata for a Tes teaching resource by ID, including title, subject, age range, price, attachments, and recent reviews.

Instructions

Get a Tes teaching resource. Returns normalized 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, which robots.txt already disallows scraping regardless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTes resource id
countryNoStorefront market for pricing/currency

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / country / enum
      Added value: +[
+  "GB",
+  "US",
+  "AU",
+  "IE",
+  "CA",
+  "NZ",
+  "UN"
+]
  2. Addedv1.16.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden, and it does so well: it discloses that attachments are metadata only, that the resource file itself is not returned, and that robots.txt blocks scraping. It stops short of describing error/pagination behavior, but this is a simple read endpoint.

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?

One dense, front-loaded sentence gets directly to the operation and return contents, with no filler. The parenthetical lists and final exclusion all carry information an agent needs.

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 covers the main return groups (facts, attachment metadata, reviews) and the key non-return (file). It is sufficient to call the tool, though it does not describe the exact JSON shape or how country affects pricing beyond the schema's one-line note.

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. The description adds meaningful value by specifying that id is the numeric id returned by tes-resource-search, which tells the agent where to obtain a valid id.

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 operation—getting one Tes teaching resource by numeric id—and enumerates the exact normalized detail it returns. It also differentiates itself from related tools by noting the id comes from tes-resource-search and that the downloadable file is not included.

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?

Tells the agent the id is the field returned by tes-resource-search, establishing a search-then-detail workflow. It does not explicitly state alternative tools to use for search or file downloads, so the guidance is clear but not fully explicit on exclusions.

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

Deploy Server

Other Tools