JobMojito

Get one of the company's reasons

get_reason

Read-onlyIdempotent

[Reasons] One decision or position status reason by id, archived ones included.

Every argument in full, with examples: get_tool_reference.

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": {
      "reason_id": "<reason_id>"
    },
    "name": "get_reason"
  }
}

Input Schema

Name	Required	Description
`type`	No	Its type, when known (decision or position_status); left out, both are searched.
`llm_model`	No	Your model id, e.g. "claude-opus-4-8"; "unknown" if unsure. For analytics.
`reason_id`	Yes	The reason (an id from list_reasons, a decision or a position lifecycle change).
`merchant_id`	No	Optional merchant to scope to. Admins and sub-merchant operators only; other callers always use their token's merchant.
`conversation_id`	No	The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

Name	Required	Description
`id`	Yes
`kind`	No
`type`	Yes
`label`	Yes
`status`	Yes
`use_count`	No
`applies_to`	No
`sort_order`	Yes
`default_key`	No
`translations`	No
`display_label`	No
`_mcp_instructions`	No	Server-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral fact — archived reasons are returned — but says nothing about error behavior or visibility/permission limits beyond what the schema states for merchant_id.

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?

Two short sentences, front-loaded with the resource tag and the single-result scope, with zero filler. The get_tool_reference pointer is compact and placed last, though it slightly displaces substantive description content.

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?

With an output schema, full annotation coverage and 100% schema description coverage, the description only needs to convey purpose and any non-obvious behavior. It does that via the archived-inclusion note, though it could say more about how to resolve an unknown id.

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 every parameter including the type enum and merchant_id scoping is already documented. The description adds no parameter meaning of its own; its only nod to arguments is delegating to get_tool_reference, which is a pointer rather than added semantics.

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?

States a specific verb and resource ('One decision or position status reason by id') and narrows scope with 'archived ones included', which distinguishes it from a listing tool. It does not name list_reasons as the sibling to use for discovery, leaving that inference to the agent.

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 'by id' and the reason_id schema text pointing back to list_reasons, and the description redirects to get_tool_reference for argument detail. There is no explicit when-not guidance, e.g. what to do if the id is unknown or the reason is not found.

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

All JobMojito tools Inspect

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.