Skip to main content
Glama

CON, Central Operating Network

Define a term

define_term
Read-only

Two-sentence definition of a Solana memecoin market term (bundled launch, sniper, dev exit, bonding curve ...) or a CON system or capability name.

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": {
      "term": "<term>"
    },
    "name": "define_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description still contributes real behavioral context by promising a 'two-sentence' result (the only disclosure of output shape, since no output schema exists) and by delimiting the term universe. It does not say how unknown or out-of-domain terms are handled.

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?

One sentence, front-loaded with the core action and the output length, with the examples packed into a parenthetical. No filler or redundant restatement of the title.

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, non-destructive lookup with no output schema, the description covers purpose, input domain, and return size, which is close to sufficient. The remaining gap is edge-case behavior for terms outside the glossary, which an agent would want to know.

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 description coverage is 0% for the single 'term' parameter, so the description must carry the load. It partially does so by giving example values, which helps an agent pick sensible input, but it leaves ambiguous whether the accepted set is a fixed glossary or arbitrary free text (the trailing '...' suggests open-ended).

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 ('Two-sentence definition of a ... term') and enumerates example term types (bundled launch, sniper, dev exit, bonding curve) plus CON system/capability names, which makes the scope unambiguous. It does not name a sibling tool or explicitly contrast with check_coin or list_systems, so it stops short of full differentiation.

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 meets an unfamiliar memecoin or CON term. There is no explicit 'use this when' statement, no exclusion of adjacent tools, and no guidance on what to do if the term is outside the glossary.

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