Skip to main content
Glama
Sign In
DecisionsSearch

DecisionsSearch

by Renzo-Tognella
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

graph.catalog.export_csv

Export the graph catalog as a CSV bundle to preserve business rules and decisions for external analysis or backup.

Instructions

Exporta catálogo do grafo como bundle CSV.

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": "graph.catalog.export_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only states that the tool exports a catalog, but does not indicate whether it is read-only, modifies state, requires permissions, or has any side effects. The agent receives no information about safety or impact.

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?

The description is a single, concise sentence that states the core purpose. It is front-loaded and efficient. However, it is so brief that it sacrifices completeness, which prevents a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and no output schema, the description should explain what the export produces (e.g., a file path, download URL, or data stream). It does not describe the return value or behavior, leaving the agent without enough context to use the tool correctly.

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?

The tool has zero parameters, and the schema coverage is 100% (trivially). The description adds no parameter information, but none is needed. Following the guideline for 0 parameters, a baseline of 4 is appropriate.

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 states the verb 'Exporta' and resource 'catálogo do grafo', specifying the output format as 'bundle CSV'. This distinguishes it from the sibling `graph.catalog.import_csv` (import). However, it does not elaborate on what constitutes a 'bundle CSV' or the scope of the export, leaving some ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives (e.g., `graph.catalog.import_csv` for importing, or other export methods). There is no mention of prerequisites, context, or scenarios where export is appropriate.

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

Deploy Server

Other Tools