Skip to main content
Glama

Veliane Discovery Plus

Veliane price

get_veliane_price
Read-onlyIdempotent

What Veliane costs: free for everyone today, planned membership options, what always stays free.

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_veliane_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds context about what information is returned (pricing details), which is useful but does not disclose other behavioral traits like rate limits or auth requirements. A 3 is appropriate given annotations carry the main behavioral load.

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?

The description is a single, front-loaded sentence that efficiently lists the pricing aspects without any wasted words. It is appropriately sized for a simple informational tool.

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

Completeness3/5

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

For a simple pricing info tool with annotations covering safety and no output schema, the description adequately conveys what content is returned. However, the lang parameter is entirely undocumented in both schema and description, leaving a gap for an agent that needs to set it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single lang parameter, and the description does not mention it at all. While the enum in the schema hints at a language selector, the description provides no meaning, format, or usage guidance, failing to compensate for the coverage gap.

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 clearly states the resource (Veliane costs) and the specific pricing aspects covered: free today, planned membership options, and what always stays free. It implicitly distinguishes from siblings like get_veliane_facts or get_veliane_feature by focusing on pricing, but does not explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives, nor any when-not conditions. The content implies usage for pricing questions, but the description offers no routing or context about when it should be selected over sibling tools.

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