Skip to main content
Glama

note_notesInfo

Retrieve detailed information for specific Anki note IDs to manage and analyze flashcard content effectively.

Instructions

Returns a list of objects containing information for each note ID provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesYesA list of note IDs.

Implementation Reference

  • Handler implementation for the 'notesInfo' tool (becomes 'note_notesInfo' after prefixing). Calls AnkiConnect API to fetch info for given note IDs.
    @note_mcp.tool(
        name="notesInfo",
        description="Returns a list of objects containing information for each note ID provided.",
    )
    async def get_notes_info_tool(
        notes: Annotated[List[int], Field(description="A list of note IDs.")],
    ) -> List[Dict[str, Any]]:
        return await anki_call("notesInfo", notes=notes)
  • Registers the note_mcp tools with 'note_' prefix into the main anki_mcp server, resulting in tool name 'note_notesInfo'.
    await anki_mcp.import_server("note", note_mcp)
  • Creates the note_mcp FastMCP instance where note tools like notesInfo are registered.
    note_mcp = FastMCP(name="AnkiNoteService")
  • Common helper function used by all tools to invoke AnkiConnect API actions, including 'notesInfo'.
    async def anki_call(action: str, **params: Any) -> Any:
        async with httpx.AsyncClient() as client:
            payload = {"action": action, "version": 6, "params": params}
            result = await client.post(ANKICONNECT_URL, json=payload)
            result.raise_for_status()                                      
            result_json = result.json()
            error = result_json.get("error")
            if error:
                raise Exception(f"AnkiConnect error for action '{action}': {error}")
            response = result_json.get("result")
                                                                 
                                                                                                         
                                                                                            
            if "result" in result_json:
                return response
            return result_json                                                                        
  • Pydantic schema for input (list of note IDs) and output (list of note info dicts).
        notes: Annotated[List[int], Field(description="A list of note IDs.")],
    ) -> List[Dict[str, Any]]:
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions returning a list of objects but doesn't disclose behavioral traits like rate limits, authentication needs, error handling, or pagination. For a tool that presumably fetches note metadata, this leaves significant gaps in understanding how it behaves operationally.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action ('returns a list of objects'), though it could be more specific. The structure is clear but lacks elaboration that might be necessary given the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'information' includes, return format, or error cases. For a tool with one parameter but potentially complex output, this leaves the agent under-informed about how to interpret results.

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 100%, so the schema already documents the 'notes' parameter as a list of note IDs. The description adds no additional meaning beyond what's in the schema—it merely restates that note IDs are provided. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool returns information for note IDs, which clarifies it's a read operation. However, it's vague about what specific information is returned ('information for each note ID') and doesn't distinguish from sibling tools like note_findNotes or note_getNoteTags. The verb 'returns' is clear but the resource scope is ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or exclusions. With sibling tools like note_findNotes and note_getNoteTags available, the lack of differentiation leaves the agent guessing about appropriate use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ujisati/anki-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server