Skip to main content
Glama

Create a concept

create_concept

Create a new concept with a name, its content, and when_to_read: the moment it should be opened.

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": {
      "name": "<name>",
      "content": "<content>",
      "when_to_read": "<when_to_read>"
    },
    "name": "create_concept"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA name that makes sense on its own, such as "Sam's job".
contentYesThe content of the concept.
when_to_readYesThe moment this concept will be needed. search_semantic matches on this text.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that the description adds nothing: no mention of whether duplicate names are allowed, whether creation is idempotent, what happens on validation failure, or how the new concept becomes searchable.

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?

A single economical sentence that front-loads the verb and lists the inputs. No filler, though it offers little beyond a restatement of the schema's required fields.

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

Completeness3/5

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

For a three-parameter creation tool with full schema coverage and annotations, the essentials are present via structured fields. The description still omits anything an agent would need to choose this tool over set_concept or to understand the retrieval consequences of the when_to_read field.

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 baseline is 3. The gloss of when_to_read as "the moment it should be opened" restates what the schema already says ("The moment this concept will be needed. search_semantic matches on this text.") without adding new meaning.

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 ("Create a new concept") and enumerates the three required inputs, so the agent knows exactly what is produced. It does not distinguish itself from nearby siblings such as set_concept or create_tag, leaving that differentiation to the names alone.

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?

There is no guidance on when to create a new concept versus updating an existing one (set_concept, update_content) or how to avoid duplicates. Usage is only implied by the verb.

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