Skip to main content
Glama

Protocol info

get_protocol_info
Read-onlyIdempotent

Live protocol parameters: loan fee, the three loan terms with their durations and buyback costs, minimum loan and deposit sizes, per-token lending limit bounds, and whether the protocol is paused.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and open-world behavior, so the bar is lower. The description still adds real value beyond them: 'Live' signals the values are current rather than cached, and surfacing 'whether the protocol is paused' is operationally important state an agent should check before acting.

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?

A single front-loaded sentence with a dense but readable field list and zero filler. Nothing is repeated from the title or schema, and nothing extraneous is included.

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?

With no output schema, the description carries the burden of describing return values, and it does so thoroughly for a zero-parameter getter. The only mild gap is that it does not state units or value formats for the fee/limit figures, though that is reasonably left to the response payload.

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 the baseline of 4 applies. The schema is an empty object and the description correctly offers no parameter discussion, which is the right call.

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 names a specific resource (live protocol parameters) and enumerates exactly what it returns: loan fee, the three loan terms with durations and buyback costs, minimum loan/deposit sizes, per-token lending limit bounds, and paused status. That field list implicitly separates it from market-level siblings like get_market and get_risk_report, though no sibling is named explicitly.

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 only implied: an agent infers it should call this when it needs fee, term, or limit constants or the pause state. There is no explicit when-to-use statement, no pointer to get_market for market-specific data, and no note that this should be consulted before building borrow/deposit transactions.

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.