Skip to main content
Glama

export_entities

Export extracted entities to CSV or JSON format with entity text, type, confidence scores, and occurrence counts for data analysis or reporting.

Instructions

Export all extracted entities to CSV or JSON format. Includes entity text, type, confidence scores, document counts, and occurrence counts. Useful for data analysis, reporting, or importing into other tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoExport format: 'csv' or 'json'csv
entity_typesNoFilter by entity types (e.g., ['hardware', 'instruction']). Leave empty for all types.
min_confidenceNoMinimum confidence threshold (0.0-1.0)
output_pathNoOptional file path to save export (if not provided, returns as string)
Behavior2/5

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

No annotations; description lacks details on output behavior (e.g., returns string vs saves file), potential data size limits, or side effects. Only states what it exports, not how.

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?

Three sentences: action/format, content, usage. No filler, efficient and clear.

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?

Adequately covers purpose and parameters but omits important context like output structure, export limits, or behavior when output_path is omitted. Missing detail for a potentially large dataset export.

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 covers all 4 parameters with descriptions (format, entity_types, min_confidence, output_path). Description adds no extra parameter insight beyond listing exported fields.

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 exports entities to CSV or JSON, lists included fields (text, type, confidence, etc.), and distinguishes from sibling extract/export tools by specifying entity data.

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?

Provides use cases (data analysis, reporting, importing) but fails to explicitly differentiate from sibling export tools like export_relationships or export_results, or advise when not to use.

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/MichaelTroelsen/tdz-c64-knowledge'

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