Skip to main content
Glama
lorsabyan

okf-mcp-server

by lorsabyan

List concepts in an OKF bundle

okf_list_concepts
Read-onlyIdempotent

List concepts from an OKF bundle, filtering by type, tag, lifecycle status, or trust. Returns summary entries without bodies, making it safe for large bundles.

Instructions

List concepts, optionally filtered by type, tag, or lifecycle status.

Returns summaries without bodies, so it is safe to call on a large bundle. Use okf_get_concept to read one in full.

Args:

  • bundle_path (string): directory containing the bundle

  • type (string, optional): exact OKF type, e.g. "Metric", "BigQuery Table", "Attested Computation"

  • tag (string, optional): exact tag

  • status ('draft' | 'stable' | 'deprecated', optional): lifecycle filter (spec §5.4)

  • trust ('unverified' | 'machine-confirmed' | 'human-reviewed', optional): trust tier (spec §5.3)

  • limit (number): 1-200, default 50

  • offset (number): default 0

  • response_format ('markdown' | 'json'): default 'markdown'

Returns: { "total": number, "count": number, "offset": number, "has_more": boolean, "next_offset": number, // present only when has_more "concepts": [{ "id": string, "title": string, "type": string, "description": string, "tags": string[], "resource": string, "status": "draft"|"stable"|"deprecated", "trust": "unverified"|"machine-confirmed"|"human-reviewed", "verified_by": string[], "verified_at": string, "updated_at": string, "stale_since": string }] }

Examples:

  • Use when: "What metrics are defined?" -> type="Metric"

  • Use when: "Which definitions has nobody verified?" -> trust="unverified"

  • Use when: "Show me anything deprecated" -> status="deprecated"

Error Handling:

  • An unmatched type or tag returns an empty list plus the values that do exist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoExact tag to filter by
typeNoExact OKF type to filter by
limitNoMaximum results
trustNoTrust tier derived from `verified` (§5.3)
offsetNoResults to skip, for pagination
statusNoLifecycle status (§5.4)
bundle_pathYesPath to the OKF bundle directory (a folder of .md files). Absolute paths are safest.
response_formatNo'markdown' for reading, 'json' for machine processingmarkdown
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint), the description discloses that it returns summaries only, is safe for large bundles, and explains error behavior for unmatched filters. This adds meaningful context without contradicting the annotations.

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?

The description is well-structured with distinct sections for overview, parameters, return format, examples, and error handling. Every section earns its place, and the key purpose is front-loaded.

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?

Despite lacking an output schema, the description provides a full inline return structure, covers all parameters, includes examples, and addresses error handling. This makes it complete for a complex listing tool.

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. The description adds value by providing examples for the type parameter (e.g., 'Metric') and clarifying the 'response_format' default, though it mostly repeats schema information.

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?

The description clearly states it lists concepts with optional filters by type, tag, or lifecycle status. It also distinguishes itself from okf_get_concept by noting it returns summaries without bodies, making it suitable for large bundles.

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?

It explicitly advises using okf_get_concept to read a concept in full, and provides concrete 'Use when' examples for type, trust, and status filters. This gives clear guidance on when to choose this tool over alternatives.

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/lorsabyan/okf-mcp-server'

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