Skip to main content
Glama
Sign In
@ainize/mcp

@ainize/mcp

Official
by ainblockchain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Teacher profile

teacher_profile
Read-only

Retrieves a data provider's teaching history and earnings on the node, showing which lessons they taught and what each paid. Free to use.

Instructions

A data provider's lessons and earnings on this node — who taught what, and what it paid them. Free.

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": {
      "address": "<address>"
    },
    "name": "teacher_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesthe teaching key address of the data provider

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered and the description earns credit only for adding that the data is scoped to 'this node' and costs nothing. It does not explain what 'this node' means (local node? network context?), whether results are truncated or paginated, or how earnings are denominated.

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 substance and closing with the cost note that actually matters for tool selection. Nothing is redundant and no filler appears.

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 read tool with no output schema, the description gives a usable sketch of the payload (lessons taught plus earnings). The remaining gap is that 'this node' is never defined and no indication of result size or completeness is given.

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 coverage is 100% and the single address parameter is fully described in-schema, so the baseline of 3 applies. The description reinforces that the address identifies a teacher/provider but adds no format, casing, or lookup-failure detail beyond the regex already in the schema.

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 the resource clearly: a data provider's lessons and earnings, elaborated as 'who taught what, and what it paid them.' That is concrete enough to distinguish it from knowledge/search siblings, but the tool name/param use 'teacher' while the description says 'data provider,' and it never explicitly contrasts itself with any sibling.

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: you'd call this to inspect a provider's teaching record and payouts. The word 'Free' hints that this is a no-cost lookup in contrast to a priced/quote flow, but the description states no when-to-use condition, no prerequisite, and no named alternative.

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