Skip to main content
Glama

atlas_list_jds

Read-onlyIdempotent

List a hiring context's job descriptions (id, title, content); the content is the jd_text the fit tools take. Free.

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": {
      "context_id": "<context_id>"
    },
    "name": "atlas_list_jds"
  }
}

Input Schema

NameRequiredDescriptionDefault
context_idYesFrom atlas_list_contexts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / context_id / description
      Previous value: -"Context ID from atlas_create_context or atlas_list_contexts"New value: +"From atlas_list_contexts"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds value beyond that with the cost signal ("Free") and by disclosing the returned field set, which matters since there is no output schema.

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?

A single sentence that front-loads the action and scope, then appends the two highest-value facts (field list, downstream use of content). Nothing is redundant or padded.

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?

For a one-parameter, read-only list tool with full annotation coverage and no output schema, the description supplies everything needed: scope, return fields, and how the content field feeds the fit tools. No meaningful gap remains.

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 context_id parameter already documents its provenance ("From atlas_list_contexts"). The description reinforces that the id scopes to a hiring context but adds no format or edge-case detail 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.

Purpose4/5

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

States a specific verb and resource ("List a hiring context's job descriptions") and even enumerates the returned fields (id, title, content). It is unambiguous about scope, though it does not explicitly name a sibling to contrast with, which keeps it just short of the top mark.

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?

Adds real routing guidance by explaining that the returned content "is the jd_text the fit tools take," telling an agent this is the prerequisite step before fit calls. "Free" also signals no credit cost, useful for cost-aware planning. No explicit when-not-use condition is given.

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