Skip to main content
Glama

Request a new token

request_token_listing
Read-onlyIdempotent

Check whether a token is accepted as collateral. If it is not, returns a pre-filled link to the Based Loans request form for the user to open and submit. Nothing is submitted automatically.

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": {
      "token": "<token>"
    },
    "name": "request_token_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesToken contract address on Base

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: it discloses that nothing is submitted automatically and that the form link is only returned when the token is rejected. The annotations already declare readOnlyHint/openWorldHint/idempotent, so the description mainly needed to resolve the 'request' framing — which it does convincingly.

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 short sentences, front-loaded with the core check and followed by the conditional outcome. Every clause earns its place, including the important 'nothing is submitted automatically' reassurance.

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-param, read-only, no-output-schema tool, this is nearly complete. The only gap is the positive case — it never says what is returned when the token is already accepted (status/boolean), leaving the agent to infer the success shape.

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?

With one parameter at 100% schema coverage (contract address on Base, with a 0x-pattern), the schema already carries the semantics. The description adds no further detail about accepted token formats or chains, so 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 concrete operation — checking whether a token is accepted as collateral — plus the conditional side effect of returning a pre-filled request-form link. This clearly separates it from build_*/get_* siblings, though it never names an alternative explicitly and the name ('request_token_listing') suggests a write that the description reframes as a read/check.

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?

Gives a clear trigger: use it to find out if a token is accepted as collateral, or to point a user at the listing-request form. There is no explicit 'do not use this for X' or named alternative, so it stops short of full routing guidance.

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.