Skip to main content
Glama

Remotejobify

Fetch

fetch
Read-onlyIdempotent

One Remotejobify job by the id search gave: who can apply, the proof line and the description.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe id from search.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is fully covered by structured data. The description adds only the payload contents ('who can apply, the proof line and the description'), which is modest added value and largely overlaps the output schema. No notes on error behavior for a bad/missing id or on data freshness.

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 a single short sentence fragment with no filler, which is good, but the structure is awkward: the core statement is buried behind a garbled relative clause, and jargon like 'the proof line' is undefined. Brevity is achieved at the cost of readability rather than through it.

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?

This is a simple one-parameter read tool with annotations and an output schema, so the description does not need to explain return values or safety. Still, for a catalog containing both 'fetch' and 'get_job', the definition should say how they differ; that omission is the main completeness 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?

With one parameter at 100% schema description coverage, the schema already explains 'id'. The description does add the useful provenance detail that the id should come from a prior search, which is slightly more than the schema states. No format, example, or validity notes beyond that, so the baseline 3 applies.

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 does identify the resource (one Remotejobify job) and the lookup key (the id from search), and it hints at returned content (who can apply, the proof line, the description). But the phrasing is convoluted ('by the id search gave') and it never differentiates itself from the sibling 'get_job', which appears to do something very similar, leaving the agent to guess which one to call.

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

Usage Guidelines3/5

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

'the id search gave' implies a prerequisite workflow: obtain an id from search first, then fetch here. That is genuine, if implicit, sequencing guidance. There is no explicit when-to-use/when-not guidance and no mention of the get_job or search_jobs siblings, so the agent cannot determine whether this or get_job is the right retrieval path.

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