Skip to main content
Glama

Get Linof's live prices

get_linof_pricing
Read-onlyIdempotent

Get the prices Linof sells at right now: the Starter, Standard and Premium plans, their packages in every currency, top-ups and the free trial, read live from Linof's pricing service. Use it for any question about cost, rather than quoting a price from memory.

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": "get_linof_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoOnly this plan. Leave out for every plan.

Output Schema

NameRequiredDescriptionDefault
packsYes
plansYes
buyUrlNo
sourceYes
topupsYes
currenciesYes
pricingPageNo
taxIncludedNo
animationSecondsYes
freeTrialAnimationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 meaningful context beyond that: the values are read live at call time ('right now'), so the agent knows not to cache or treat results as static, and it discloses the breadth of the returned catalog. Return shape is covered by the output schema.

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 sentences, zero waste, with the capability stated first and the usage directive second. The enumeration of covered items is dense but each item is informative about scope.

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?

Annotations supply the safety profile, the output schema supplies the return shape, and the single parameter is fully documented. The description fills the remaining gaps an agent needs: data freshness, what the catalog includes, and when to prefer it over recalling prices.

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 coverage is 100% and the single optional parameter has an enum with its own description ('Only this plan. Leave out for every plan.'). The description's listing of the three plan names mirrors the enum rather than adding new semantics, so the baseline 3 applies.

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?

Specific verb plus resource: 'Get the prices Linof sells at right now', then enumerates exactly what is covered (Starter/Standard/Premium plans, packages in every currency, top-ups, free trial) and the source (Linof's pricing service). This distinguishes it from the doc-oriented siblings fetch_linof_doc and search_linof_docs, which return documentation rather than live prices.

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?

'Use it for any question about cost, rather than quoting a price from memory' gives a clear positive trigger and an explicit anti-pattern. It does not explicitly name the sibling doc tools as the alternative for non-price questions, but the live-vs-documentation contrast is strongly implied by 'read live from Linof's pricing service'.

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