Skip to main content
Glama

brainfile

by io.brainfile

get_starter_file

Get the REAL Brainfile free-tier starter files — the on-ramp that turns generic Claude into a project that remembers you. Full text, no account needed. Files: INTERVIEW-ME.md (first-session interview that personalizes your CLAUDE.md), START-HERE.md (orientation + first prompt), CLAUDE.starter.md (starter operating-system playbook). Omit 'name' to get all three.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoWhich starter file to fetch. Omit for all three.

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, but description adds key traits: 'Full text, no account needed', and lists files. Does not mention rate limits or authentication, but tool is read-only and non-destructive, so adequate.

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; first states purpose, second lists files and usage note. No filler, front-loaded with key info.

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?

Complete for a simple tool: explains what it retrieves, how to use the parameter, and lists contents. No output schema needed given clarity.

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 covers 100% with enum, but description adds valuable context: omission returns all three files. This goes beyond the schema's individual file descriptions.

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?

Description clearly states verb ('get') and resource ('starter files'), names specific files, and explains behavior. Distinguishes from sibling tools like get_freshness_sample.

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?

Indicates when to use (on-ramp for personalization, no account needed) but does not explicitly state when not to use or mention alternatives. However, sibling tools are distinct, making context clear.

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

All brainfile toolsInspect
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

A4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: retrieving a freshness sample, getting starter files, and listing pack contents. There is no ambiguity or overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (get_freshness_sample, get_starter_file, list_pack_contents), making them predictable.

Tool Count4/5

Three tools is on the low end but appropriate for a focused retrieval server that provides access to specific resources without needing CRUD operations.

Completeness4/5

The tools cover listing all pack contents and retrieving starter files and the freshness sample. However, direct access to other pack files is not provided (intentionally via trial), which is a minor gap.

Resources