Skip to main content
Glama
Sign In
Toleno Network MCP Server

Toleno Network MCP Server

Official
by tolenonetwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_security_info

Addresses safety concerns by providing Toleno Network's security measures, trust indicators, and upcoming milestones. Use this to verify trustworthiness.

Instructions

Get Toleno Network security and trust information: security measures, trust indicators, and upcoming milestones. Use this when users ask "is Toleno safe?", "is it trustworthy?", "is it a scam?" etc. This is a public tool — no API key required.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4.5/5.0
Behavior4/5

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

Discloses that the tool is public and requires no authentication. While no annotations are present, the description appropriately characterizes it as a read-only info tool. Could be improved by mentioning data freshness or source, but adequate given simplicity.

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 efficient sentences. First sentence states purpose with specific details; second sentence provides usage context and an important caveat (no API key). Every sentence adds value without redundancy.

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?

Given zero parameters and no output schema, the description fully covers what the tool does, when to use it, and an important property (public). No gaps remain for this simple tool.

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?

Tool has zero parameters, so schema coverage is 100%. The description does not need to explain parameters; the baseline of 4 applies as no additional param context is necessary.

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?

Description clearly states it retrieves security and trust information, listing specific items (security measures, trust indicators, upcoming milestones). It also provides example user queries, distinguishing it from sibling tools like get_project_info or get_faq.

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?

Explicitly says 'Use this when users ask...' with concrete examples, and notes it's a public tool with no API key required. No explicit 'when not to use' but the specified queries provide clear guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools