Skip to main content
Glama
Sign In
mguttmann

action1-mcp-server

by mguttmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get endpoint general info

action1_get_endpoint
Read-onlyIdempotent

Retrieve general information for a specific endpoint using its unique identifier. Access the endpoint's info block, platform data, and current connectivity status to manage infrastructure.

Instructions

Fetch the general info block for a single endpoint, plus derived platform and connectivity.online flags.

Input Schema

NameRequiredDescriptionDefault
org_idNoOrg UUID.
endpoint_idYesEndpoint UUID.
response_formatNoOutput format. Default markdown.

Output Schema

NameRequiredDescriptionDefault
sourceNostring
generalNoobject
platformNostring
connectivityNoobject

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.6.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / endpoint_id / pattern
      Previous value: -"^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$"New value: +"^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • addedOutput schema / properties / connectivity
      Added value: +{
+  "description": "object"
+}
    • addedOutput schema / properties / general
      Added value: +{
+  "description": "object"
+}
    • addedOutput schema / properties / platform
      Added value: +{
+  "description": "string"
+}
    • addedOutput schema / properties / source
      Added value: +{
+  "description": "string"
+}
  2. First observedv0.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and an output schema exists. The description adds mild value by naming the derived fields returned (platform, connectivity.online), but says nothing about permissions, errors for unknown endpoint IDs, or cross-org scoping.

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?

A single well-formed sentence that front-loads the action and resource with no filler. Slightly terse for a tool with three parameters and an org scoping option, but nothing is wasted.

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

Completeness4/5

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

With rich annotations, a full output schema, and 100% schema coverage, the description's minimal scope statement is sufficient to call the tool correctly. Only the lack of sibling differentiation keeps it from being fully complete.

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 description coverage is 100%, so endpoint_id, org_id, and response_format are already fully documented in the schema. The description only implies the endpoint_id requirement ('a single endpoint') and adds no syntax or format detail, matching the baseline 3.

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 gives a specific verb (fetch) and resource (general info block for a single endpoint) and notes the derived platform and connectivity.online flags. It does not, however, distinguish this from siblings like action1_list_endpoints or action1_search_endpoints, so an agent must infer that this is the single-endpoint detail call.

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?

Usage is implied by the phrase 'a single endpoint,' suggesting it is the per-endpoint detail lookup versus the list/search siblings, but no explicit when-to-use or when-not guidance is provided.

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