Skip to main content
Glama
Sign In
freeagent-mcp-server

freeagent-mcp-server

by samaxbytez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

freeagent_create_estimate

Create a new estimate, quote, or proposal in FreeAgent with contact, date, currency, line items, comments, reference, and payment terms.

Instructions

Create a new estimate in FreeAgent

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": {
      "contact": "<contact>",
      "estimate_type": "<estimate_type>",
      "dated_on": "<dated_on>",
      "currency": "<currency>"
    },
    "name": "freeagent_create_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactYesContact URL
commentsNoComments on the estimate
currencyYesCurrency code
dated_onYesEstimate date (YYYY-MM-DD)
referenceNoEstimate reference
estimate_typeYesType of estimate
estimate_itemsNoJSON array of estimate items with item_type, quantity, price, description
payment_terms_in_daysNoPayment terms in days

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.3.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=false, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that — no mention of side effects, required preconditions, whether the estimate starts in draft status, or what the response contains.

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?

A single short sentence with the action front-loaded and no wasted words. However, its brevity is under-specification rather than disciplined conciseness, so it does not fully earn a 5.

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

Completeness2/5

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

For a mutation tool with 8 parameters (4 required), no output schema, and only minimal annotations, the description should explain required inputs, default behavior, and what gets created. None of that context is present, leaving the agent dependent entirely on the schema.

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% with 8 documented parameters, so the schema already carries the parameter burden. The description contributes no additional meaning, such as the expected URL format for contact or the structure of the JSON-string estimate_items field, which would have been valuable for a nested-JSON parameter flattened into a string.

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

Purpose3/5

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

The description states a clear verb and resource ('Create a new estimate'), but that is essentially a restatement of the tool name with the vendor appended. It does nothing to distinguish this from siblings such as freeagent_update_estimate or freeagent_create_invoice beyond what the name already conveys.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus the many sibling update/list/get estimate tools, nor any prerequisites such as needing an existing contact URL or choosing between Estimate, Quote, and Proposal types. An agent must infer all of this from the name and schema alone.

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

Deploy Server

Other Tools