Free-trial AI fleet spend meter. Quote agent fleet spend from token usage. 100 calls or 14 days. No auth. Official MCP Registry: io.github.mtardy90-sudo/bootlace-ai-spendmap.
The server exposes only one tool with a clearly specific purpose: producing a spend quote for an agent fleet. There is no overlapping functionality for an agent to misselect.
spendmap_quote uses the server's product prefix plus a single action word, and with only one tool there is no conflicting convention or mixed naming style.
A single tool feels far too thin for a server branded as a SpendMap, even if the quote endpoint is narrowly scoped. The count only supports one interaction rather than a coherent toolkit.
The tool covers only one-off quoting with no evident way to persist, retrieve, update, or analyze spend data. For a spend-mapping domain, core lifecycle and analysis operations are missing.
Return a list-price spend quote for a fleet of agents. No auth. Free-trial / stress-test Bootlace AI meter: 100 calls or 14 days from first use, whichever hits first. POST JSON: agents, callsPerAgentPerDay, inputTokensPerCall, outputTokensPerCall, cachePct, days, model. Cache applies to input tokens only. Convert to prepaid ACH human retainers (Cut List Lite $1,500 / 3 days, Agent Spend Audit $5,000 / 5 days, ContextCheck $5,000 / 5 days, Spend Cap Pack $2,500 when listed).
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Period length in days. | |
| model | No | Bundled list-price model id. One of: gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-luna, claude-opus-5, claude-sonnet-5, claude-haiku-4.5, grok-4.6, grok-4.3, grok-build-0.1. | |
| agents | No | Number of agents in the fleet. Defaults to the on-page calculator value. | |
| cachePct | No | Cached input percent (0–100). Cache applies to input tokens only. Alias: cachePercent, cache. | |
| inputTokensPerCall | No | Input tokens per call. Alias: tokensIn, in. | |
| callsPerAgentPerDay | No | Calls per agent per day. Alias: callsPerDay, calls. | |
| outputTokensPerCall | No | Output tokens per call. Alias: tokensOut, out. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, so the safe, non-destructive nature is already known. The description adds valuable behavioral context beyond annotations: no authentication required, free-trial call/time limits, and that cache applies only to input tokens. There is no contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The core purpose and meter constraints are front-loaded and compact. However, the 'Convert to prepaid ACH human retainers' segment with detailed pricing is ambiguous and not clearly tied to invoking the tool, which costs clarity without earning its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description provides essential call information: HTTP method, parameter names, auth needs, and trial limits. However, there is no output schema, and the description does not explain the shape or contents of the returned quote beyond 'list-price spend quote.' The retainer-pricing sentence further muddies completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and includes aliases for every parameter, so the schema carries the full semantic load. The description mostly restates the parameter list and the cache rule already present in the schema, adding little new meaning. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Opens with a specific verb+resource: 'Return a list-price spend quote for a fleet of agents.' This unambiguously states what the tool does and is not a tautology of the name. No sibling tools exist, so differentiation is not required.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly frames when this tool is appropriate: for list-price quotes, with no auth, and within a free-trial/stress-test meter context ('100 calls or 14 days from first use'). It does not list exclusions or alternatives, but with no siblings that is acceptable. The 'Convert to prepaid ACH human retainers' sentence adds confusing context rather than clear usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
spendmap_quoteClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity – fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge – works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge – works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
