Skip to main content
Glama
Sign In

Phulax

by pro.phulax
OverviewDiscussionsAdmin

Estimate a change order

estimate_change_order
Read-only

Prices a scope change on an existing Phulax project (materials + labor + 10% contingency) and returns a title, description, amount and cost breakdown. It is an estimate only: nothing is saved or sent. Counts toward the daily AI limit.

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": {
      "project_id": "<project_id>",
      "change_description": "<change_description>"
    },
    "name": "estimate_change_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesPhulax project id (from list_projects or create_estimate).
change_descriptionYesThe change in scope, e.g. "Upgrade the shower to a curbless walk-in with a linear drain".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations: discloses the pricing composition (materials + labor + 10% contingency), enumerates the return payload, confirms no persistence and no sending, and flags the daily AI limit as a constraint. Missing only what happens when the limit is exhausted or on invalid project ids.

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 tight sentences, front-loaded with the core action and followed by the behavioral caveats. No filler or repeated information.

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?

With no output schema, the description correctly enumerates the return fields, and it covers cost composition, side-effect-free behavior, and the rate limit. Error behavior and the maxLength constraint are left to the schema, which is reasonable for a simple two-parameter tool.

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 already explains both project_id and change_description with an example, so the description can only add the pricing context. It adds nothing parameter-specific beyond what the schema states.

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: 'Prices a scope change on an existing Phulax project', plus the pricing formula and the returned fields. It implicitly separates itself from create_estimate via 'nothing is saved or sent', but never names that sibling, so the differentiation requires inference.

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?

The 'estimate only: nothing is saved or sent' clause hints at when to prefer this over a persisting estimate, but no explicit when-to-use or when-not-to-use rule or alternative tool is named. Guidance is implied rather than stated.

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

All Phulax toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources