Skip to main content
Glama
Procured MCP Server

Procured MCP Server

procured_guide

Explains how to navigate Procured and sign in, then manage quotes, invoices, crew visits, job photos, inventory, and business reports; call this first for task-specific guidance.

Instructions

How to work in Procured (manage quotes, invoices, crew visits, job photos, inventory and business reports): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Procured, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied. The description implies an informational guide by mentioning screens and a sign-in link, but it does not explicitly state that the tool is read-only, has no side effects, requires no authentication, or returns instructions rather than performing actions. It adds some behavioral context but leaves key traits implicit.

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?

The definition is front-loaded with its purpose and ends with the critical "Call this first" directive. The parenthetical domain list is dense but useful; the phrase "its screens and the sign-in link" is slightly awkward but not wasteful.

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?

For a simple guide tool with one optional parameter, no annotations, and no output schema, the description is reasonably complete: it names the covered areas, mentions screens and sign-in link, and tells the agent to call it first. It could be stronger by clarifying read-only behavior and how the task input influences the response.

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 schema already explains the sole parameter as "What you want done in Procured, in your words." The description never mentions the task parameter, so it adds no meaning beyond the schema; baseline 3 applies because the schema does the work.

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?

The description states the resource clearly: how to work in Procured, including screens and the sign-in link, plus covered domains like quotes, invoices, crew visits, job photos, inventory, and business reports. It is recognizable as an onboarding/guide tool, though it does not explicitly differentiate itself from the procured_* siblings beyond saying to call it first.

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?

"Call this first" gives an explicit when-to-use instruction and establishes ordering. It does not provide when-not guidance or name specific alternative tools, so it stops short of full usage routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.