Skip to main content
Glama
Sign In
tie-mcp-server

tie-mcp-server

by taherkaraki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_directory_by_infrastructure

Retrieve a directory instance by providing the directory ID and infrastructure ID as path parameters.

Instructions

Get directory instance by id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "infrastructureId": "<infrastructureId>",
      "id": "<id>"
    },
    "name": "get_directory_by_infrastructure"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter: id
infrastructureIdYesPath parameter: infrastructureId

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'get' implying read-only, but lacks details on return format, authentication needs, rate limits, or any side effects.

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

Conciseness2/5

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

Too brief to be helpful; a single sentence with no structure. While concise, it sacrifices necessary information such as distinguishing features or expected output.

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?

For a simple get tool with no output schema, the description fails to mention return value or the relationship between parameters. It is incomplete given the lack of annotations and schema hints.

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?

Input schema covers both parameters with descriptions (Path parameter). The description adds no extra meaning beyond the schema, which already has 100% coverage. Baseline score of 3 applies.

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 'Get directory instance by id.' which is clear but does not differentiate from sibling tools like get_directory or list_directories_by_infrastructure. The name includes 'by_infrastructure', implying context, but the description lacks specifics.

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 versus alternatives. No mention of prerequisites, exclusions, or comparison to other get/list tools.

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