Skip to main content
Glama
Sign In
Metrx MCP Server

Metrx MCP Server

by metrxbots
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Job Contract

metrx_get_job_contract
Read-onlyIdempotent

Retrieve an agent's current job contract by workload—objectives, acceptance criteria, KPIs, budget, owner, and version history—or an empty state with the next action.

Instructions

Read an agent's job contract: its current version per workload (objective, unit of work, acceptance criteria, KPI target, budget, owner) and the full append-only version history. An agent with no contract returns an explicit empty state with the next action. Read-only. Requires an API key with the 'read' scope.

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": {
      "agent_key": "<agent_key>"
    },
    "name": "metrx_get_job_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_keyYesThe agent_key (the X-Agent-ID string), not the UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: the history is append-only, an empty result is an explicit state carrying a next action, and an API key with the 'read' scope is required — a real auth prerequisite not visible in the schema.

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?

Three tight sentences, front-loaded with the payload contents before the edge case and the auth note. 'Read-only.' is largely redundant with readOnlyHint=true, a small amount of wasted space in an otherwise efficient definition.

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?

There is no output schema, so the description carries the return-value burden — and it does, enumerating the contract fields and the append-only history, plus the empty-state behavior. Nothing an agent needs in order to call this correctly or interpret the result is missing.

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 coverage is 100% and the single parameter's schema description already warns that agent_key is the X-Agent-ID string rather than the UUID. The description adds no further parameter meaning, so the 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?

The description opens with a specific verb and resource ('Read an agent's job contract') and enumerates the payload fields returned (objective, unit of work, acceptance criteria, KPI target, budget, owner) plus the version history. Combined with the draft/set siblings, an agent can tell this is the read path without opening any 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 establishes the read context clearly and even covers the edge case of an agent with no contract, promising an explicit empty state with a next action. It does not explicitly name metrx_draft_job_contract or metrx_set_job_contract as the write alternatives, so the when-not guidance is implied by 'Read-only' rather than stated.

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

Deploy Server

Other Tools