Enhanciar — company brain

get_page

Fetch a single wiki page from the key's workspace.

Returns {category, name, content} — content is the full markdown body including YAML frontmatter. Returns {error: "..."} if the page doesn't exist.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`page`	No
`path`	No
`slug`	No
`title`	No
`category`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 30, 2026
- addedInput schema / properties / category / default
```
Added value: +""
```
- removedInput schema / properties / category / type
```
Removed value: -"string"
```
- addedInput schema / properties / name / default
```
Added value: +""
```
- removedInput schema / properties / name / type
```
Removed value: -"string"
```
- addedInput schema / properties / page
```
Added value: +{
+  "default": "",
+  "title": "Page"
+}
```
- addedInput schema / properties / path
```
Added value: +{
+  "default": "",
+  "title": "Path"
+}
```
- addedInput schema / properties / slug
```
Added value: +{
+  "default": "",
+  "title": "Slug"
+}
```
- addedInput schema / properties / title
```
Added value: +{
+  "default": "",
+  "title": "Title"
+}
```
- removedInput schema / required
```
Removed value: -[
-  "category",
-  "name"
-]
```
First observedSep 20, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the return shape and the nonexistent-page error case, which is genuinely useful. It says nothing about permissions, whether lookup is case-sensitive, or what happens with an invalid category, leaving key behaviors opaque.

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 purpose sentence is front-loaded, and the Args block is tight and scannable. Near-optimal size, though the Returns section partially duplicates information an output schema already covers.

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 six-parameter tool, the description documents only two parameters and all six are optional with no stated precedence, so an agent cannot be confident which argument to populate. The output schema exists, so the return description is a minor redundancy rather than a gap.

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 0%, so the description must compensate. It does add real value for two parameters — the eight allowed `category` values (an enum absent from the schema) and the slug format for `name` (no .md extension) — but four schema parameters (page, path, slug, title) are never mentioned, so the agent cannot tell whether they are aliases or distinct inputs.

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 (fetch a single wiki page) with scope (from the key's workspace), so the agent knows exactly what it retrieves. It references list_pages/search_wiki only as sources for the `name` argument rather than as alternatives for selection, so it never explicitly says when this beats a search call.

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?

Usage is implied: the `name` argument is described as coming from list_pages/search_wiki, which sketches a list-then-fetch workflow. There is no explicit when-to-use/when-not statement and no guidance on choosing this over query or search_wiki when the page slug is unknown.

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

All Enhanciar — company brain tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?