Skip to main content
Glama

Energy North Journal

Prepare a job post

post_a_job
Read-onlyIdempotent

Prepare a job for the person to post on Energy North: returns a link that opens the Energy North post-a-job form already filled with the trade, postcode and job details, so local verified tradespeople can reply. The person checks the details and posts it themselves; nothing is posted by this tool.

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": {
      "trade": "<trade>"
    },
    "name": "post_a_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
tradeYesThe trade needed, e.g. "electrician", "plumber", "roofer".
detailsNoWhat needs doing, in the person's words, up to 1000 characters.
postcodeNoUK postcode of the job, if known, e.g. "N11 1AB".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description earns credit by explaining the mechanism behind that safety profile: the tool only returns a link, the person reviews the details and posts themselves, and 'nothing is posted by this tool.' That is exactly the behavioral detail an agent needs to avoid telling a user their job is already live, and it is fully consistent with readOnlyHint.

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?

Two sentences, no filler, and the most important fact — that the output is a prefilled external form link — is front-loaded before the no-side-effects caveat. Nothing repeats the title or restates the name.

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 three-parameter, non-destructive tool with no output schema, the description covers the missing piece by describing the return value (a link opening a prefilled form) and the handoff to the human. An agent has everything needed to call it and to narrate the result to a user correctly.

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 the schema already documents trade, details and postcode with examples. The description echoes those three fields (trade, postcode, job details) without adding syntax, format, or fallback guidance (e.g. what happens if postcode is omitted despite being optional), which is the expected baseline when the schema carries the load.

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?

The description names a specific verb and resource ('Prepare a job ... on Energy North') and, critically, states what the tool produces: a prefilled link to an external post-a-job form. That return artifact distinguishes it cleanly from siblings like find_tradespeople and list_trades, which involve searching rather than composing a listing.

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?

Usage is clearly implied and largely spelled out: this is for when someone wants local verified tradespeople to reply to a job, and the last sentence makes explicit that the human completes the posting. It stops short of naming an alternative tool or stating an explicit 'do not use this if' condition, so it sits just below the top band.

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