Skip to main content
Glama
Sign In

MindDory Brain

by com.minddory
OverviewDiscussionsAdmin

Get card detail

get_card
Read-only

Single card detail by word (case-insensitive). Returns translation, mastery, and last 10 events.

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": {
      "word": "<word>"
    },
    "name": "get_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage tag of the word: base ISO with an optional region (en, en-us, pt-br). Omit it and the user's own primary learning language is used.
wordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lang / description
      Added value: +"Language tag of the word: base ISO with an optional region (en, en-us, pt-br). Omit it and the user's own primary learning language is used."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral details beyond that: lookups are case-insensitive and the result includes translation, mastery, and the last 10 events. Since there is no output schema, these return details meaningfully set expectations. It does not cover not-found behavior, but enough is disclosed.

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 deliver the purpose, lookup behavior, and expected return fields with no filler or redundancy. Every phrase in the description adds useful information.

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 simple read-only single-card lookup with two parameters and no output schema, this description is mostly complete: it identifies the key parameter, mentions case-insensitivity, and enumerates return contents. It could add a short note on not-found behavior or a clearer 'use this when' hint, but the current level is solid for this low-complexity tool.

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 50%; the schema documents 'lang' thoroughly, while 'word' only has length constraints. The description clarifies that 'word' is the lookup key and case-insensitive, adding some meaning beyond the schema. However, it does not fully compensate for all param semantics and does not mention lang behavior beyond what the schema already says.

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?

The description clearly identifies the operation as 'Get single card detail by word', with a specific resource (card), a specific lookup key (word), and explicit scope (a single card). This distinguishes it from sibling list-oriented tools like get_known_words and get_active_vocab.

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?

The usage context is implied: use this tool when you need the detail of one card by its word. However, it does not explicitly say when not to use it, mention prerequisites, or contrast with sibling tools such as check_words or get_known_words. Given the context is clear but exclusions are absent, an implied-usage score is appropriate.

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

All MindDory Brain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources