JobMojito

Get a tool's full reference

get_tool_reference

Read-onlyIdempotent

The full definition of one JobMojito tool: its complete description, and every argument with all its options and examples (part=result: every field it returns). tools/list carries short versions; this one has the options of an argument, its exact format and examples.

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": {
      "tool": "<tool>"
    },
    "name": "get_tool_reference"
  }
}

Input Schema

Name	Required	Description	Default
`part`	No	arguments (default): every argument in full; result: what the tool returns; all: both.	arguments
`tool`	Yes	The tool to describe.
`llm_model`	No	Your model id, e.g. "claude-opus-4-8"; "unknown" if unsure. For analytics.
`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	Default
`_mcp_instructions`	No	Server-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 10, 2026

addedInput schema / properties / part / anyOf

Added value: +[
+  {
+    "enum": [
+      "arguments",
+      "result",
+      "all"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / part / enum

Removed value: -[
-  "arguments",
-  "result",
-  "all"
-]

removedInput schema / properties / part / type
```
Removed value: -"string"
```

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / tool / enum

Previous value: -[
-  "add_candidate_note",
-  "create_interview",
-  "create_persona",
-  "dismiss_candidate_duplicate",
-  "duplicate_interview",
-  "duplicate_position",
-  "finish_media_upload",
-  "generate_component_styles",
-  "generate_interview_report",
-  "generate_interview_url",
-  "get_candidate",
-  "get_catalogue_directory",
-  "get_component_style_guide",
-  "get_interview_definition",
-  "get_interview_result_details",
-  "get_merchant_status",
-  "get_portal_configuration",
-  "get_report",
-  "list_avatars",
-  "list_candidate_filters",
-  "list_candidates",
-  "list_catalogue_directories",
-  "list_document_requests",
-  "list_interview_results",
-  "list_interviews",
-  "list_knowledge_base_documents",
-  "list_languages",
-  "list_media_files",
-  "list_report_fields",
-  "list_reports",
-  "list_segments",
-  "list_sub_merchants",
-  "list_tasks",
-  "manage_candidate_tag",
-  "manage_media_file",
-  "manage_media_folder",
-  "manage_meeting_slot",
-  "manage_segment",
-  "merge_candidates",
-  "preview_candidate_merge",
-  "publish_portal_stylesheet",
-  "report_technical_issue",
-  "request_another_interview_attempt",
-  "request_candidate_documents",
-  "run_report",
-  "save_catalogue_directory",
-  "save_component_style",
-  "save_report",
-  "save_task",
-  "set_assessment_result",
-  "set_candidate_tags",
-  "set_interview_state",
-  "set_knowledge_base_document_interviews",
-  "set_position_process",
-  "start_media_upload",
-  "submit_feature_request",
-  "update_document_request",
-  "update_interview",
-  "update_portal_configuration",
-  "update_position_step",
-  "upload_knowledge_base_document"
-]New value: +[
+  "add_candidate_note",
+  "create_interview",
+  "create_persona",
+  "dismiss_candidate_duplicate",
+  "duplicate_interview",
+  "duplicate_position",
+  "finish_media_upload",
+  "generate_component_styles",
+  "generate_interview_report",
+  "generate_interview_url",
+  "get_candidate",
+  "get_catalogue_directory",
+  "get_component_style_guide",
+  "get_interview_definition",
+  "get_interview_result_details",
+  "get_merchant_status",
+  "get_portal_configuration",
+  "get_reason",
+  "get_report",
+  "list_avatars",
+  "list_candidate_filters",
+  "list_candidates",
+  "list_catalogue_directories",
+  "list_document_requests",
+  "list_interview_results",
+  "list_interviews",
+  "list_knowledge_base_documents",
+  "list_knowledge_base_stores",
+  "list_languages",
+  "list_media_files",
+  "list_reasons",
+  "list_report_fields",
+  "list_reports",
+  "list_segments",
+  "list_sub_merchants",
+  "list_tasks",
+  "list_users",
+  "manage_candidate_tag",
+  "manage_media_file",
+  "manage_media_folder",
+  "manage_meeting_slot",
+  "manage_segment",
+  "merge_candidates",
+  "preview_candidate_merge",
+  "publish_portal_stylesheet",
+  "report_technical_issue",
+  "request_another_interview_attempt",
+  "request_candidate_documents",
+  "run_report",
+  "save_catalogue_directory",
+  "save_component_style",
+  "save_knowledge_base_store",
+  "save_reason",
+  "save_report",
+  "save_task",
+  "set_assessment_result",
+  "set_candidate_tags",
+  "set_interview_state",
+  "set_knowledge_base_document_interviews",
+  "set_position_process",
+  "start_media_upload",
+  "submit_feature_request",
+  "update_document_request",
+  "update_interview",
+  "update_portal_configuration",
+  "update_position_step",
+  "upload_knowledge_base_document"
+]

AddedNov 9, 2026

TDQS

A3.9/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, so safety is fully covered. The description adds useful context about what the payload contains (full argument options, examples, and returned fields via part=result) but says nothing about response size, pagination, or that the output is reference text rather than live data.

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?

Front-loaded with the core purpose and compact overall, with the tools/list contrast in a single clause. The phrasing 'this one has the options of an argument, its exact format and examples' is slightly tangled and mildly redundant with the opening clause, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the description still sketches them. The analytics-only parameters (llm_model, conversation_id) are left to the schema, which is appropriate; the only real gap is any note about response volume when part=all is requested.

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 all four parameters including the part enum and the analytics fields are already documented in the schema. The description restates part=result behavior but adds no format or edge-case detail beyond what the schema provides; baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource: returns the full definition of one named JobMojito tool, covering its description, arguments with options and examples, and (for part=result) its return fields. It explicitly contrasts itself with tools/list, which 'carries short versions', so an agent can distinguish the two without opening either 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 implies the selection rule clearly: use this when the short version from tools/list is insufficient and you need an argument's options, exact format, or examples. It stops short of an explicit 'do not use this for X' exclusion or stating that this is a two-step lookup, so it is strong but not complete.

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.