Skip to main content
Glama
IEZhu

Agents-Core

by IEZhu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Load cognitive implants

load_implants
Read-only

Load cognitive implants to enhance reasoning: choose a predefined task bundle (debugging, analysis, creative, planning) or search by query for mental models and strategies.

Instructions

Load cognitive implants (mental models, reasoning strategies).
Two modes — provide ONE of:
  - task_type: predefined bundle (debugging | analysis | creative | planning)
  - query: free-form semantic search across all implants

task_type bundles:
  debugging  → chain-of-code, reflexion, react
  analysis   → step-back-prompting, chain-of-verification
  creative   → analogical-prompting, generated-knowledge
  planning   → plan-and-solve, skeleton-of-thought

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryNo
task_typeNoOptional task type to load implants for instead of a query.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv26.10.14+1807

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond that: two mutually exclusive input modes and the exact composition of each bundle. It does not disclose what happens if neither mode is supplied or whether loaded implants persist in the session.

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?

Front-loads the purpose, then structures the two modes and bundle contents as scannable bullets. The bundle listing is not filler — it carries parameter information absent from the schema — so every line earns its place.

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?

An output schema exists, so return values need no explanation, and the description adequately covers modes and bundle composition for a 3-param, 0-required tool. The remaining gaps are the undocumented default behavior when no mode is passed and the meaning of 'limit'.

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?

Schema description coverage is only 33% (only task_type is documented in the schema), and the description compensates well: it explains query as a free-form semantic search and supplies the actual enum values for task_type, which the schema lacks (0 enums). The 'limit' parameter remains undocumented in both schema and description, keeping it from a 5.

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?

States a specific verb and resource ('Load cognitive implants') and immediately defines what they are ('mental models, reasoning strategies'). The two-mode structure (task_type vs query) and the bundle contents make it fully distinguishable from sibling tools like route_and_load or get_agent_context.

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 states 'provide ONE of' the two modes, which is strong routing guidance for mode selection, and names concretely what each task_type bundle returns. It stops short of saying when to prefer this tool over siblings (e.g. route_and_load) or which mode fits which situation, so no full 5.

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