Skip to main content
Glama
devkindhq

machship-mcp

by devkindhq

Get All Quotes

machship_get_quotes
Read-onlyIdempotent

Retrieve all quotes for a specific company. Provide the company ID to get a list of quotes with IDs, references, and statuses.

Instructions

Returns all quotes for a given company.

Args:

  • companyId (number): Company ID

  • response_format ('json' | 'markdown'): Output format (default: 'json')

Returns: Array of quote summary objects: { "id": number, "reference": string, "status": string, "createdDate": string }

Examples:

  • Use when: "List all quotes for company 123"

  • Use when: You need a quote ID to pass to machship_get_quote for full details

  • Don't use when: You want to create a new quote (use machship_create_quote instead)

Error Handling:

  • Error 404: companyId does not exist or is not accessible

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdYesCompany ID
response_formatNoOutput format: 'json' (default) or 'markdown'json
Behavior4/5

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

Annotations confirm read-only, idempotent, non-destructive behavior; description adds error handling (404 for invalid companyId) and return format, which is useful context beyond annotations.

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?

Well-structured with summary, args, returns, examples, and error handling sections; every sentence adds value and is front-loaded with main purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple listing tool, the description covers purpose, parameters, return structure, error cases, and usage guidance; no output schema needed as return format is specified.

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?

Schema coverage is 100%, but description repeats parameters with examples (default 'json' output) and links companyId to error handling, adding marginal value over schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Returns all quotes for a given company', uses specific verb and resource, and distinguishes from siblings like machship_get_quote and machship_create_quote through examples.

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

Usage Guidelines5/5

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

Provides explicit 'Use when' and 'Don't use when' sections, names alternative tool (machship_create_quote) and complementary tool (machship_get_quote), and indicates required parameter (companyId).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/devkindhq/machship-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server