Skip to main content
Glama

EX & GO marketplace

Account links

account_links
Read-only

Where on exgo.io to do what this connector cannot: open a shop (storefront with its own subdomain), buy a promotion or the Business plan, start a live show, pay for a safe deal, verify a phone, manage API tokens, read the developer docs. Returns direct links; send the person there when they ask to sell, promote, pay or set up a shop, and tell them the listing tools here need a signed-in account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the crucial behavioral facts that this is a hand-off helper, that it returns links rather than performing the actions, and that the agent should relay an explanation about signed-in accounts. That is meaningful context beyond the annotations. Minor tension: a link-out tool is annotated openWorldHint=false, but since it only returns URLs without external interaction the description does not contradict it.

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?

Purpose is front-loaded in the first clause, followed by a task list and then the routing instruction. The enumerated task list is long and the opening sentence is dense, but each item maps to a distinct user intent, so little is wasted.

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?

With no parameters, no output schema, and thin annotations, the description carries the full burden and does so: it explains the return value (direct links), the scope of covered tasks, and the follow-up message to give the user. Nothing an agent needs to call and act on this tool is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description instead spends its words on what the returned links point to, which is the more useful information here.

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?

The description names a concrete verb and output ('Returns direct links') and a concrete resource ('Where on exgo.io to do what this connector cannot'), then enumerates the covered tasks. It also distinguishes itself from the sibling listing tools by noting those need a signed-in account, so an agent can route correctly without inspecting the schema.

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

Usage Guidelines5/5

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

It gives an explicit trigger list ('send the person there when they ask to sell, promote, pay or set up a shop') and an explicit boundary ('what this connector cannot' do). Both when-to-use and when-not-to-use are stated, which is rare and directly actionable.

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