Crawlora MCP

tes_resource_shop

Read-only

Fetch a Tes teaching-resource seller's shop profile and one page of resource listings by username. Use tes_resource_search or tes_resource_detail to find the author username; use tes_resource_detail for one resource or tes_job_employer for an employer profile.

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

Input Schema

Name	Required	Description
`page`	No	One-based page
`subject`	No	Subject tab to filter the listing to -- see the shop's own page for the current set
`username`	Yes	Tes author username

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.

Changed3 schema fields changedOct 7, 2026
- addedInput schema / properties / page / description
```
Added value: +"One-based page"
```
- addedInput schema / properties / subject / description
```
Added value: +"Subject tab to filter the listing to -- see the shop's own page for the current set"
```
- addedInput schema / properties / username / description
```
Added value: +"Tes author username"
```
First observedOct 7, 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 safety profile is covered. The description adds the useful scoping fact that only one page of listings is returned, but says nothing about pagination progression, result caps, or error behavior on an unknown username.

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 filler, purpose front-loaded before the sibling routing advice. Every clause earns its place.

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?

An output schema exists, so return values need no explanation, and the description fully covers purpose, required input, scope, and alternative tools. Only edge-case behavior (unknown username, page bounds) is left unaddressed, a minor gap.

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 the schema itself documents page ('One-based page'), subject, and username. The description reinforces the username framing and the one-page limit, but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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), resource (a Tes teaching-resource seller's shop profile plus one page of their resource listings), and scope (one page, by username). This lets an agent distinguish it from tes_resource_search and tes_resource_detail without opening the 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 tells the agent how to obtain the required username (via tes_resource_search or tes_resource_detail) and routes to the right sibling for adjacent needs (tes_resource_detail for a single resource, tes_job_employer for an employer profile). When-to-use and alternatives are both spelled out.

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.