Skip to main content
Glama

The Local Upgrade — Software Engineering

Review procurement and delivery practices

get_procurement_information
Read-onlyIdempotent

Engagement process, data handling, supplier-review topics and authority boundaries for RFPs and subcontracting.

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": "get_procurement_information"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 and openWorldHint=false, so the safety and side-effect profile is fully covered. The description adds the content domain (policy/authority material for RFPs and subcontracting) but says nothing about whether this is static guidance versus live case data, what form the answer takes, or any scope limits. That is modest added value on top of complete annotations.

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?

It is a single compact phrase with no filler or redundancy, and the domain qualifier 'for RFPs and subcontracting' usefully narrows scope up front. The terseness comes at the cost of clarity rather than from padding, so it is efficient but not exemplary.

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?

For a zero-parameter, no-output-schema reference tool, the bar is low, and the topic list conveys roughly what the agent will get back. Still, the description leaves unclear whether the result is a document, a policy summary, or a checklist, and offers no signal for choosing this over prepare_engagement_brief or request_proposal in a procurement sequence.

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 semantics for the description to carry; the baseline of 4 applies. The description does not mislead by implying inputs that don't exist.

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 enumerates content topics (engagement process, data handling, supplier review, authority boundaries) for RFPs and subcontracting, which gives a rough sense of subject matter. However, it is a noun-phrase fragment with no verb – it never states that the tool retrieves or returns reference guidance rather than performing an action. It hints at a distinct scope from siblings like review_engineering_evidence, but doesn't explicitly differentiate.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites, and no named alternative among the siblings (prepare_engagement_brief, request_proposal, review_engineering_evidence). The agent must infer that this is the reference-lookup step in a procurement workflow purely from the topic list.

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