Skip to main content
Glama

Verako

Get the signup link for an offer

get_signup_link
Read-onlyIdempotent

Get the link for one offer from a comparison (electricity, savings or deposits). The link is the provider's own page unless the result says affiliate: true. Nothing about the user is sent.

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": {
      "offer_id": "<offer_id>"
    },
    "name": "get_signup_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
offer_idYesThe offer_id from a comparison, e.g. 'lyse-energi-as/10215'

Output Schema

NameRequiredDescriptionDefault
urlYes
networkYes
productYes
offer_idYes
supplierYes
affiliateYes
commissionYes
disclosureYes
personal_data_sentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), so the description's added value is the affiliate caveat and the privacy note that nothing about the user is sent. Those are genuinely useful disclosures beyond the annotations. What is missing is any statement about link lifetime, expiry, or whether the URL is stable across calls, which matters for an idempotent-looking link fetch.

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, front-loaded with the action, then the affiliate caveat, then the privacy note. Every sentence carries information and nothing is padded. Could be marginally tighter by folding the provider-page caveat into the first sentence.

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?

For a one-parameter read tool with an output schema, this covers what is needed to invoke it correctly plus the key non-obvious return nuance (affiliate flag) and the privacy guarantee. The only gap is where exactly offer_id should be sourced from, which is left implicit.

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 offer_id property already documents the format with an example, so the description adds little. 'One offer from a comparison' confirms the provenance of the ID but not its syntax or alternative sources, so the baseline 3 applies.

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 verb and resource ('Get the link for one offer') and scopes it to comparison results (electricity, savings, deposits), which distinguishes it from the compare_* and explain_* siblings by implication. The scope is clear enough to select the tool without opening the schema, though it never explicitly contrasts itself with those siblings.

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?

Usage is implied rather than stated: the agent infers the tool applies to a single offer obtained from a comparison, and the schema's offer_id example reinforces the flow. There is no explicit when-not guidance, no mention of what to do for a non-comparison offer, and no named 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.

Resources