Skip to main content
Glama

Redstick: construction tech on the record

Jobs

list_jobs
Read-only

The jobs on site that tools on Redstick's record are filed under, each with its stage of the work. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds 'Free' (no cost to call) and that results are grouped by stage of work, which is genuine context beyond the structured fields. It does not say whether results are complete or paginated, so the addition is modest.

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

Conciseness3/5

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

Only two short sentences, so length is not the issue, but the key noun phrase is buried in a long relative clause and the core action ('list') never appears. The trailing 'Free' is useful but placed as an afterthought rather than front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No parameters and no output schema exist, so the description must carry the burden of explaining what a returned job looks like; it only says each has a 'stage of the work'. It omits ordering, whether the list is exhaustive, and how jobs relate to the tools they group, leaving gaps for a zero-arg reference tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning for the description to convey. Baseline 4 applies; the schema is empty and fully described.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

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

The description identifies the resource ('jobs on site') and notes what each entry carries ('its stage of the work'), so an agent can infer this returns a job taxonomy. But the verb is never stated, and the phrasing 'the jobs on site that tools on Redstick's record are filed under' is convoluted enough that the listing action must be inferred. No differentiation from siblings such as list_systems or list_trades.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives among the sibling list tools. At best, 'filed under' hints that this is a reference/grouping lookup rather than a search, but the agent must supply that reasoning itself.

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