Skip to main content
Glama
Sign In

Arbituro

by com.arbituro
OverviewDiscussionsAdmin

Get a job

get_job
Read-onlyIdempotent

Get one job in full: its description, the plan a person approved for how to do it when there is one, the done-when clauses that define completion and the state each is in, who it is assigned to, the job it is part of, how many parts it has, and what has been spent on it.

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": {
      "project": "<project>",
      "job": "<job>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesThe job's key, e.g. FLAIR-12.
projectYesThe project's key, e.g. FLAIR.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive operation. Beyond that, the description adds substantial return-content context by naming the included fields: description, approved plan, done-when clauses and their states, assignee, parent job, part count, and spend.

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

Conciseness4/5

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

The description is front-loaded with the core action and avoids unnecessary framing. It is a single long sentence with a dense field list, which slightly reduces readability but every clause carries relevant return-content information.

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?

For a simple read-only retrieval tool with complete parameter documentation and annotations covering safety, the definition supplies the main missing context by describing what the returned job record contains. It does not cover error behavior or output formatting, but no output schema exists and the core call context is present.

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 both parameters are already documented with examples in the schema. The description does not add syntax, constraints, or meaning beyond what the schema provides, so the baseline score of 3 applies.

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

Purpose4/5

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

The description states a specific verb and resource: "Get one job in full", and enumerates what the job record includes. It distinguishes the tool from listing-style siblings by emphasizing a single job and full detail, though it does not explicitly name alternatives such as list_jobs or job_history.

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?

Usage is implied by "Get one job in full": use this when you need the complete record for a known job. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative for cases like listing jobs or checking history.

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

All Arbituro toolsInspect
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.

Resources