Skip to main content
Glama
Sign In

Foundingbird

by com.foundingbird
OverviewDiscussionsAdmin

List packages and prices

list_packages
Read-onlyIdempotent

The packages and add-ons for one service, step by step, with prices in the firm's currency and the item ids estimate_quote takes. Some steps only apply under a condition (listed under conditions); pass flags to see the steps as that customer would.

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": {
      "flow": "<flow>"
    },
    "name": "list_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowYesThe service: "incorporation-sdn-bhd" registers a new Sdn Bhd; "switch-in-sdn-bhd" moves an existing Sdn Bhd to this firm as its company secretary. get_firm_overview lists what this firm offers.
flagsNoAnswers to the conditions some package steps depend on, as list_packages reports them, e.g. {"requires_virtual_office": true} when the customer has no business address of their own.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish this is a read-only, idempotent, non-destructive, closed-world listing, so the safety profile is covered. The description adds useful behavior beyond that: prices are expressed in the firm's currency, output includes condition-gated steps, and flags change which steps appear. It still does not describe result shape or ordering, which matters more here because there is no output schema.

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?

Two compact sentences that lead with what is returned and follow with the condition/flag behavior. The parenthetical '(listed under conditions)' is mildly self-referential and 'step by step' is vague, but there is no padding or redundant restatement of the title.

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 two-parameter read tool with no output schema, the description covers the essentials: what is returned (packages, add-ons, steps, prices, item ids), currency, and how conditional steps are surfaced. The one gap is that 'conditions' is named as if it were a familiar output field without being fully explained, leaving the agent to infer the response structure.

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 coverage is 100%; both flow's enum meanings and the flags object with a concrete example are fully documented in the schema. The description reinforces that flags correspond to the conditions the tool reports and that ids feed estimate_quote, but adds no syntax or key-level detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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: it returns packages and add-ons for one service, with prices in the firm's currency and the item ids that estimate_quote consumes. That cross-reference to estimate_quote distinguishes it from the quote tool. 'Step by step' is slightly loose about what a step is, keeping it one notch below a fully crisp statement.

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?

Gives real context for the flags parameter: pass them 'to see the steps as that customer would,' and conditional steps are only shown when their condition is answered. It also implies the natural sequence (call this before estimate_quote to obtain item ids), but it never states an explicit exclusion or names a sibling to use instead for other needs such as get_firm_overview.

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

All Foundingbird 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