Skip to main content
Glama
Procured MCP Server

Procured MCP Server

procured_open

Opens a Procured page in your signed-in Cloud Browser to access and manage quotes, invoices, crew visits, job photos, inventory, and business reports.

Instructions

Open a Procured page in your signed-in Cloud Browser (default https://app.procured.us/login) to work with manage quotes, invoices, crew visits, job photos, inventory and business reports.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://app.procured.us/login

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the default target URL and that the browser session is signed in, but says nothing about what happens to the currently loaded page, whether navigation is in-place or a new tab, or how failures (expired session, bad URL) surface.

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?

One sentence with the verb and default URL front-loaded, so it reads quickly. The trailing clause 'to work with manage quotes, invoices, crew visits...' is grammatically awkward and adds breadth without helping an agent decide or call correctly.

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 single-parameter open/navigate tool this is close to sufficient, and the default URL is covered. With no output schema and no description of what is returned (e.g., page content or a success indicator), an agent cannot infer the result of the call.

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?

There is a single optional parameter with 100% schema description coverage already stating the default. The description merely restates that default and adds no interpretation of the URL format, allowed schemes, or whether external domains are permitted, so the schema-does-the-work 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: open a Procured page in the signed-in Cloud Browser, with the default URL named. The trailing list of business areas is vague context rather than scope, and it does not distinguish this from siblings like procured_read, which reads a page that must presumably already be open.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: opening a page is the natural entry point before procured_click, procured_type, or procured_read, and 'signed-in Cloud Browser' hints at a session prerequisite. No explicit when-to-use, when-not, or ordering guidance is given, and no alternative is named.

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