StackFast FractWin Expert Brain

Fetch StackFast Reader Result

fetch

Read-onlyIdempotent

Fetch a StackFast Brain result or an authorized immutable session artifact by id through the AI6 MCP reader plane. Use the explicit safe shape with id, page, and page_size, for example fetch({ id: "brain:12345", page: 1, page_size: 12000 }) or fetch({ id: "artifact:474", page: 1, page_size: 12000 }); continue with next_page until complete is true.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Result id returned by the reader plane, for example brain:12345 or an authorized artifact:474. Prefer this over the legacy aid field.
`aid`	No	Legacy compatibility field for direct brain aid. Prefer id plus explicit page and page_size.
`page`	Yes	Required explicit one-based page number. Use 1 for the first page.
`next_page`	No	Alias for page when following the next_page value returned by a prior fetch call.
`page_size`	Yes	Required explicit maximum characters returned in this page. Use 12000 unless a smaller page is needed.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`ok`	No
`url`	Yes
`page`	No
`text`	Yes
`title`	Yes
`message`	No
`complete`	No
`metadata`	No
`page_end`	No
`next_page`	No
`page_size`	No
`error_code`	No
`page_start`	No
`page_sha256`	No
`total_chars`	No
`total_pages`	No
`content_sha256`	No
`supported_call_shapes`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 30, 2026

changedInput schema / properties / id / description

Previous value: -"Result id returned by the search tool, for example brain:12345. Prefer this over the legacy aid field."New value: +"Result id returned by the reader plane, for example brain:12345 or an authorized artifact:474. Prefer this over the legacy aid field."

Changed1 schema field changedJul 10, 2026

changedInput schema / properties / id / description

Previous value: -"Result id returned by the search tool, for example brain:15033. Prefer this over the legacy aid field."New value: +"Result id returned by the search tool, for example brain:12345. Prefer this over the legacy aid field."

Changed5 schema fields changedJul 9, 2026

changedInput schema / properties / aid / description

Previous value: -"Optional direct brain aid. Equivalent to id when id is omitted."New value: +"Legacy compatibility field for direct brain aid. Prefer id plus explicit page and page_size."

changedInput schema / properties / id / description

Previous value: -"Result id returned by the search tool, for example brain:12022."New value: +"Result id returned by the search tool, for example brain:15033. Prefer this over the legacy aid field."

changedInput schema / properties / page / description

Previous value: -"One-based page number for large entries. Defaults to 1."New value: +"Required explicit one-based page number. Use 1 for the first page."

changedInput schema / properties / page_size / description

Previous value: -"Maximum characters returned in this page. Defaults to 8000 and is capped at 12000."New value: +"Required explicit maximum characters returned in this page. Use 12000 unless a smaller page is needed."

changedInput schema / required

Previous value: -[]New value: +[
+  "id",
+  "page",
+  "page_size"
+]

Changed5 schema fields changedJul 9, 2026

addedInput schema / properties / next_page

Added value: +{
+  "description": "Alias for page when following the next_page value returned by a prior fetch call.",
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / error_code
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ok
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / supported_call_shapes

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed14 schema fields changedJul 8, 2026

addedInput schema / properties / aid

Added value: +{
+  "description": "Optional direct brain aid. Equivalent to id when id is omitted.",
+  "type": "string"
+}

addedInput schema / properties / page

Added value: +{
+  "description": "One-based page number for large entries. Defaults to 1.",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / page_size

Added value: +{
+  "description": "Maximum characters returned in this page. Defaults to 8000 and is capped at 12000.",
+  "maximum": 12000,
+  "minimum": 1000,
+  "type": "integer"
+}

changedInput schema / required

Previous value: -[
-  "id"
-]New value: +[]

addedOutput schema / properties / complete
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / content_sha256
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / next_page

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / page
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / page_end
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / page_sha256
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / page_size
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / page_start
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / total_chars
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / total_pages
```
Added value: +{
+  "type": "integer"
+}
```

AddedJun 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavior beyond annotations by explaining the paged fetch loop with next_page and complete, and by characterizing artifacts as immutable and authorized.

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?

Two sentences front-load the core purpose, immediately give a safe usage template, and close with the pagination termination condition. There is no filler; every phrase earns its place.

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?

The description is complete enough for a read-only paged fetch tool: id format, required parameters, page size bounds, pagination continuation, and termination condition are all covered. An output schema exists, so the return shape does not need to be restated in prose.

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 100%, so the baseline is 3, but the description adds concrete examples of the expected id format ('brain:12345', 'artifact:474'), a suggested page_size of 12000, and clarifies the pagination flow. This goes beyond the schema descriptions by showing a complete valid invocation.

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?

The description clearly specifies a concrete action—'Fetch a StackFast Brain result or an authorized immutable session artifact by id'—and names the resource type and access plane. It is distinct from sibling search tools because it is explicitly id-based, though it never names an alternative sibling.

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?

The description gives clear operational guidance: use the explicit id, page, and page_size shape, and continue following next_page until complete is true. It does not state when to choose this tool over search or other siblings, but the id-based usage context is clearly implied.

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

All StackFast FractWin Expert Brain tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.6/5.0

Disambiguation1/5

Several tools are exact duplicates (talent_scout_my_profile_status and talent_scout_profile_status have identical descriptions), and eight estimator_estimate_* tools share the same generic description with no differentiation. This will cause misselection.

Naming Consistency3/5

Most tools follow a snake_case verb_noun pattern, but there are inconsistencies: the duplicate profile tools have different naming (my_profile vs profile), and `fetch`/`search` are single-word verbs. Predictability is hampered by these deviations.

Tool Count2/5

65 tools is excessive for a coherent set, especially with many tools covering overlapping actions across multiple unrelated domains (AI receptionist, estimator, talent scout, GrowthOS). The count could be trimmed significantly.

Completeness3/5

The tool surface is broad and covers many lifecycle operations (create, read, export, record), but the duplicate tools and identical descriptions for estimator operations make it unclear whether all needed operations are present. Some expected operations like delete/update are missing for certain resources.

Resources

Need Help?