Skip to main content
Glama

Read one of your completed private results

history_private_jobs_detail
Read-onlyIdempotent

Private data for this authenticated caller only. Exact-payer completed private jobs in the current store; explicit history:read required. Bounded scan/continuation, unknown provenance and NULL own spend/creator settlement remain explicit. No wallet selector, public report/share link, model prompt, research, source fetch, signer, purchase or mutation authority.

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": "history_private_jobs_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesExact private research ID: prv_ followed by 64 lowercase hex digits; preserve it and keep it private.

Output Schema

NameRequiredDescriptionDefault
rowYes
scopeYes
formatYes
resultYes
walletYes
capabilitiesYes
qualificationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"Exact private research ID: prv_ followed by 64 lowercase hex digits; preserve it and keep it private."
    • addedOutput schema / properties / row / properties / id / description
      Added value: +"Exact private research ID: prv_ followed by 64 lowercase hex digits; preserve it and keep it private."
  2. Added

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real value: an auth/scope requirement (history:read, caller-scoped data), bounded scan/continuation behavior, explicit handling of unknown provenance and NULL own-spend/creator-settlement values, and a clear enumeration of absent capabilities (no wallet selector, share link, prompt, source fetch, signer, purchase or mutation). The continuation/provenance clauses are opaque jargon with no detail on what the caller sees, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the scope constraint, so nothing is buried. However, it is written as a chain of dense noun-phrase fragments separated by semicolons and dashes, which is hard to scan and forces the agent to parse negations rather than read a stated action.

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

Completeness3/5

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

With an output schema, one fully-documented parameter and read-only annotations, the structured data carries most of the load, and the auth requirement is covered. Gaps remain around behavior when the ID is unknown, not the caller's, or outside the current store, and around how continuation surfaces in the response — points an agent would need to call this confidently.

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?

There is a single parameter and schema description coverage is 100%, with the prv_ + 64-hex pattern and privacy handling fully documented in the schema itself. The description adds no meaning about the id (no format reminder, no not-found or non-owned behavior), so it meets only the baseline for a fully-documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states a verb or says plainly that it returns the detail record for one private job; it opens with a scope statement ("Private data for this authenticated caller only") and a dense qualifier ("Exact-payer completed private jobs in the current store"). The resource is identifiable but only by inference from the name/title, and it never distinguishes itself from siblings like history_private_jobs_list or history_private_jobs_export.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only actionable guidance is the prerequisite "explicit history:read required." There is no when-to-use routing: nothing says to call this after history_private_jobs_list, or that export/list are the alternatives for enumeration or bulk retrieval, even though three close siblings exist.

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.