Skip to main content
Glama

Feeds

Estimate the monthly cost of following an account

estimate_cost
Read-only

Credits and US dollars a month to follow one X or LinkedIn account at a check interval. Free, no account needed. Example: {"sourceType":"linkedin","handle":"https://www.linkedin.com/company/example","cadenceMinutes":60}. Uses the posting rate Feeds has seen for the account, or postsPerDay, or 1 post a day.

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": {
      "sourceType": "<sourceType>",
      "cadenceMinutes": "<cadenceMinutes>"
    },
    "name": "estimate_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoThe account, to use the posting rate Feeds has seen
sourceTypeYestwitter for X accounts, linkedin for LinkedIn profiles and company pages
postsPerDayNo
cadenceMinutesYesMinutes between checks. Minimum 5 for X, 60 for LinkedIn

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint=false, so safety is already covered; the description adds genuinely new context by stating the call is free and requires no account. It also discloses the cost-model fallback chain (observed posting rate, then postsPerDay, then 1 post/day), which is real behavioral information not present in 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences plus a compact example, with the output units front-loaded. No filler, though the opening sentence is slightly elliptical grammatically ('Credits and US dollars a month to follow...').

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

Completeness4/5

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

With no output schema, the description still communicates the return units (monthly USD and credits) and the estimation basis, which is the core of what an agent needs. Minor gaps remain, such as behavior for an unrecognized handle or whether the response breaks the estimate down by component.

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 75%, so most parameters are documented structurally. The description still adds precedence semantics that the schema lacks: handle uses the posting rate Feeds has seen, but postsPerDay can override, and a 1-post-per-day default applies otherwise. The inline JSON example further clarifies how sourceType, handle, and cadenceMinutes combine.

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?

The description states a specific computation ('Credits and US dollars a month to follow one X or LinkedIn account at a check interval'), so an agent knows exactly what the tool returns. It does not name or contrast with the sibling preview_posts, so differentiation must be inferred from the tool name alone.

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?

'Free, no account needed' tells the agent it can call this freely, and the example shows a realistic invocation shape. However, there is no explicit when-to-use versus when-not guidance and no mention of the sibling preview_posts as a related alternative.

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.