Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

fetch_unique_node_data_and_schema

Fetch unique node data and schema from the Compliance Graph to answer compliance questions and enable automated remediation actions.

Instructions

Fetch unique node data and schema

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_namesNo
unique_property_valuesNo
neo4j_schemaNo
errorNo

Implementation Reference

  • Constant definition URL_RETRIEVE_UNIQUE_NODE_DATA_AND_SCHEMA = '/v1/llm/retrieve_unique_node_data_and_schema' - the API endpoint path used by the tool.
    URL_RETRIEVE_UNIQUE_NODE_DATA_AND_SCHEMA = "/v1/llm/retrieve_unique_node_data_and_schema"
    URL_EXECUTE_CYPHER_QUERY = "/v1/llm/execute_cypher_query"
    URL_RETRIEVE_GRAPH_SCHEMA_RELATIONSHIP = "/v1/llm/retrieve_schema_and_relationship"
Behavior2/5

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

No annotations are provided, and the description only says 'Fetch,' implying a read-only operation but offering no details about side effects, auth needs, or return behavior beyond what might be in the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief (one sentence), which is concise, but it sacrifices informativeness. It is not sufficiently developed for its purpose.

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?

With a required 'question' parameter and no annotations, the description should provide more detail about usage and expected input. An output schema exists but does not compensate for the lack of parameter context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter 'question' has no description in the schema (0% coverage) and no explanation in the description. The phrase 'unique node data and schema' does not clarify what the question parameter does.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Fetch unique node data and schema,' which indicates a fetch operation but does not clarify what 'unique node' refers to in this context or distinguish it from numerous sibling fetch tools.

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 on when to use this tool compared to alternatives like fetch_checks or fetch_assets_summary. The description lacks explicit context or exclusions.

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/ComplianceCow/cow-mcp'

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