Skip to main content
Glama
theSharque
by theSharque

Set Entry

set-entry

Create or update a project entry for a concrete fact, with kind, title, summary, and optional module link.

Instructions

Entries need vertical structure: create modules via set-project-architecture / set-module-details before or when adding entries. Set refs.moduleName to an existing module name from list-modules. Run validate after edits to find entries-without-modules, entry-unlinked, or empty slices. Creates or updates one canonical project fact (entry). Use when you discovered a concrete fact while working. Do not use for module structure—use set-module-details. Do not copy module.description into summary; link via refs.moduleName only. Upsert: pass id to update, or omit id to match by kind+title or create new. Example: kind=http-endpoint, title='POST /orders', summary='Creates order', refs.moduleName='orders', refs.files=['src/OrderController.java'].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoProject id from list-projects if workspace path may differ; defaults to MCP_PROJECT_ID
idNoEntry uuid; omit to upsert by kind+title or create new
kindYesFree-form type: http-endpoint, glossary, entity, flow, script, godot-scene, etc. Builtin slice list-slices shows recommended kinds per sliceId
titleYesShort unique label for search, e.g. 'POST /orders' or 'Order'
summaryYes1-2 sentences; not a module essay—only this fact
payloadNoKind-specific extra fields only, e.g. method/path for APIs, steps for flow
refsNo
tagsNoOptional labels for get-slice query filtering

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
entryIdYes
messageYes
reminderNo
warningNo
suggestedModuleNamesNo
Behavior4/5

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

No annotations provided, so description carries full burden. Describes upsert behavior, linking constraints (refs.moduleName must exist), and warns against misusing fields (e.g., summary vs description). Could add more on permissions or side effects.

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?

Long but every sentence adds value; front-loads the critical prerequisite about module creation. Could be slightly more concise, but no wasted content.

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

Completeness5/5

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

Covers prerequisites, post-actions, upsert behavior, parameter constraints, and common mistakes. Output schema exists, so return values are already described. Completes the picture for a complex tool with 8 parameters.

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 coverage is high (88%), so baseline 3. Description adds semantic guidance beyond schema, e.g., explaining that refs.moduleName links by name, not summary, and giving an example of kind, title, summary usage.

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?

Explicitly states 'Creates or updates one canonical project fact (entry)' and distinguishes from sibling tools like set-module-details. Provides concrete examples (e.g., http-endpoint) and clear resource scope.

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

Usage Guidelines5/5

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

Clearly specifies when to use ('discovered a concrete fact'), when not to ('do not use for module structure'), and alternatives ('use set-module-details'). Includes prerequisites and post-actions like 'Run validate after edits'.

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/theSharque/mcp-architect'

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