Skip to main content
Glama

Modulos AI Governance Platform

get_job_description

Read-only

Returns the full job description of one role at Modulos: what the job is and what it requires. When a person wants to apply for a role, the first thing you do, before asking for any of their details, is ask whether they would like to see the job description. If they say yes, call this tool and show them job_description in full, exactly as it is: do not summarise, shorten or comment 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": {
      "role_id": "<role_id>"
    },
    "name": "get_job_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
role_idYesRole id from list_open_roles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description is not the only source of the safety profile. It adds real behavioral context: the return must be shown verbatim with no summarising or commentary, and the role_id is expected to originate from list_open_roles. It does not cover failure behavior for an unknown or malformed role_id.

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

Conciseness5/5

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

Purpose is front-loaded in the first clause, followed by the usage sequence in a logical order. The verbatim-display instruction is directive but earns its place by preventing a common failure mode (summarising the description).

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?

There is no output schema, so the description must indicate the return value, and it does by naming the job_description field and requiring full display. For a single-parameter read tool this is nearly complete, with only error handling on an invalid role_id left unaddressed.

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% and the role_id description already says 'Role id from list_open_roles' with a UUID pattern. The tool description does not add any meaning about the parameter beyond the schema, so the baseline of 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?

States a specific verb and resource ('Returns the full job description of one role at Modulos') and scopes the content ('what the job is and what it requires'). This clearly separates it from list_open_roles, which supplies the role_id, and from the application-flow siblings.

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

Usage Guidelines5/5

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

Gives explicit sequencing ('before asking for any of their details'), a precondition (ask whether they want to see it), and the trigger ('If they say yes, call this tool'). It also states how to present the result, leaving little to inference.

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