Skip to main content
Glama

get_work

Read-onlyIdempotent

Use after search_works or when the user supplies a work_id. Returns the canonical work page URL and public supplier summary. No buyer, contact, price or inquiry data is included.

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": {
      "work_id": "<work_id>"
    },
    "name": "get_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_idYesPublic work id, e.g. wk_...

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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description earns its keep by adding a content-boundary disclosure — that no buyer, contact, price or inquiry data is returned — which is not expressed anywhere in the structured fields.

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?

Three short sentences: the trigger first, the return value second, the exclusion third. Nothing is redundant and no sentence restates the tool name.

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?

With no output schema, the description must carry the return-value burden and does so precisely. For a single-parameter, read-only lookup whose annotations cover safety, an agent has everything needed to invoke it correctly.

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?

With one parameter at 100% schema coverage, the schema already defines work_id and even supplies a wk_... example. The description only adds provenance (the id comes from search_works or the user), which is useful but minimal beyond the schema.

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?

It names a specific verb (get/returns) and resource (work), and states exactly what comes back: the canonical work page URL and public supplier summary. Naming 'search_works' as the preceding step distinguishes it from that sibling without the agent needing to open either schema.

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 two explicit trigger conditions: after a search_works call, or when the user supplies a work_id. It also scopes out buyer, contact, price and inquiry data, which implicitly routes those needs elsewhere, though it does not name the alternative tools for them.

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.

Resources