Skip to main content
Glama

ServiceFront

ServiceFront pricing

getPricing
Read-onlyIdempotent

ServiceFront's own plans and limits (Free $0, Basic $59): what each includes and what's never charged for. No input. The same content as https://servicefront.ai/pricing.md.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getPricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context: the result is static, requires no input, and mirrors a public marketing page at a named URL, which tells an agent the content is non-sensitive and stable.

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 short sentences, front-loaded with scope and concrete pricing anchors, followed by the canonical source URL. Nothing is redundant or padded.

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 static, zero-argument read tool with no output schema, the description supplies everything needed: subject, scope, that no input is required, and where the identical authoritative content lives. The shape of the return value is the only thing left unsaid, which is low-risk here.

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?

Zero parameters, so the baseline is 4; the description explicitly states 'No input,' which correctly sets the expectation that no arguments are required.

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 resource (ServiceFront's own plans and limits) and even previews the content (Free $0, Basic $59, what's included, what's never charged for). 'ServiceFront's own' implicitly separates it from quote/custom-pricing siblings, though it never names them explicitly.

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 content description implies the use case (questions about the vendor's plans, tiers, or billing limits), but there is no explicit when-to-use statement and no routing against getQuote or getBusinessInfo. 'No input' is a parameter note, not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources