Skip to main content
Glama

Hyreflow

hyreflow_knowledge_index

Read-only

List every page of this workspace's second brain, the notes Hyreflow keeps about the business (roles, ideal customer, messaging). Each entry has slug, title, type, folder, status, tags and updated_at, without the page text. build is the state of the latest build (running, done or failed) and null when none started. Empty when no brain has been built. Persona Search filter pages hold the titles, locations, skills, keywords and seniority for a people search with the provider tools. Folders by task: Candidate personas, Search filters and Pains for sourcing, Angles, Pains, Triggers and Proof for outreach, Client ICP, Client personas, Offers and Desks for BD. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hyreflow_knowledge_index"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, non-destructive), so the description's value is in what it adds: entries exclude page text, `build` reports running/done/failed and is null when no build has started, and the result is empty when no brain exists. It also states the call is free, which annotations do not convey.

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?

Front-loaded with purpose, then return fields, then build state, then the folder taxonomy. The folder-by-task sentence is the weakest element — a long enumeration that is useful orientation but the least economical part. Otherwise no filler.

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?

With no output schema and no parameters, the description must carry the return-value burden, and it does: field list, build-state values and the null/empty cases. The folder taxonomy and the Persona Search filter note round out what an agent needs to interpret results.

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?

Zero parameters, so the schema carries nothing to explain. The description instead characterizes the returned entry shape (slug, title, type, folder, status, tags, updated_at) and the Persona Search filter variant, which is more useful than parameter prose would be.

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?

Opens with a specific verb and resource ('List every page of this workspace's second brain') and immediately glosses what a brain is (notes about the business: roles, ideal customer, messaging). It is distinguishable from knowledge_read/search in practice, though it never names those siblings to sharpen the contrast.

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 only implied: an agent can infer this is the discovery/index step before reading a page by slug. There is no explicit statement of when to prefer this over hyreflow_knowledge_search or hyreflow_knowledge_read, and no prerequisites or exclusions.

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.