Skip to main content
Glama

FitMySoft — Field Service Software Prices

by com.fitmysoft

Field service software pricing lookup

get_field_service_software_pricing
Read-onlyIdempotent

Get current, human-verified pricing for field service management software (Jobber, Housecall Pro, Workiz, ZenMaid, ServiceTitan, Service Fusion, FieldPulse): every plan with monthly and annual price, users included, per-user fees quoted verbatim, and trials. Use when someone asks what Jobber, Housecall Pro, ServiceTitan or similar costs, asks for the price of scheduling, booking, invoicing or accounting software for a cleaning, maid, HVAC, plumbing, electrical or lawn care business, asks about alternatives to one of these products, or compares two of them against each other.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
softwareYesSoftware name, e.g. "Jobber", "Housecall Pro", "ZenMaid"

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent semantics. The description adds that the data is current and human-verified, and details what fields are returned (plans, monthly/annual price, users, per-user fees, trials), which gives useful context beyond the 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?

Two dense sentences: first states the action and scope, second provides use cases. No redundancy, and information is front-loaded.

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 lookup tool with no output schema, the description adequately explains what the response will contain (all pricing details) and when to use it. The agent has enough information to select and invoke the tool correctly.

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?

The schema covers the single parameter with an example, but the description goes further by listing all valid software names, giving the agent concrete options. This is additional semantic value beyond the schema's one example.

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?

The description clearly states the tool retrieves current, human-verified pricing for field service management software and enumerates the exact products covered (Jobber, Housecall Pro, etc.). It also lists the specific pricing attributes (monthly/annual price, users, per-user fees, trials), making it distinct from the sibling comparison tool.

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?

Provides explicit use cases: when someone asks for costs, pricing for scheduling/booking/invoicing software, alternatives, or comparisons. However, it does not mention when not to use this tool or explicitly compare it to the sibling tool 'compare_field_service_software'.

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

All FitMySoft — Field Service Software Prices toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one compares pricing based on team size and budget, returning total costs, while the other provides detailed plan pricing for specific software. There is no overlap or ambiguity in their intended use cases.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern: 'compare_field_service_software' and 'get_field_service_software_pricing'. The naming is predictable and clearly indicates the action and subject.

Tool Count3/5

With only two tools, the server feels slightly thin for a general-purpose API, though it fits the narrow focus on pricing and comparison. Each tool serves a distinct role, but the count is on the lower end of what might be expected.

Completeness5/5

For the stated domain of field service software pricing, the tools cover both obtaining detailed pricing and comparing costs by team size, with no obvious missing operations. The surface is complete for its intended use.

Resources