Get Endpoint
get_endpointRead-onlyIdempotent
Authenticated tool to get endpoint.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| appId | Yes | ||
| endpointId | Yes |
Relin
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating a safe, read-only operation. The description adds 'Authenticated', which is already implied by the tool's context. It does not contradict annotations.
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 extremely short (5 words) and front-loaded. While it is concise, it sacrifices necessary detail. It is structurally fine but under-informative.
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 no output schema and 0% parameter coverage, the description is incomplete. It fails to mention what the tool returns, error conditions, or any behavioral details beyond the minimal statement.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description offers no explanation of the parameters (appId, endpointId) such as their format, purpose, or how they relate to the endpoint. The agent must rely solely on the parameter names.
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 endpoint' which is a clear verb+resource combination. However, it is vague because it does not specify what information about the endpoint is retrieved. The sibling 'list_endpoints' suggests this tool returns a single endpoint's details, but the description does not confirm this.
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 like 'list_endpoints' or 'update_endpoint'. The only hint is the word 'Authenticated', but that is a common trait among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.8/5.0
Disambiguation4/5
Most tools have distinct purposes, but there is some overlap between `list_messages`, `list_recent_events`, and `list_message_attempts`, and between `replay_event` and `replay_events`. However, the descriptions generally clarify differences.
Naming Consistency4/5
The naming mostly follows a verb_noun pattern (create_, list_, get_, update_, delete_), with consistent snake_case. A few tools like `rotate_endpoint_secret` and `upsert_event_type` deviate but still use verb_noun structure.
Tool Count2/5
With 52 tools, the set is extremely large and may overwhelm agents. While the domain is complex, this many tools reduce coherence and make selection more difficult.
Completeness4/5
The tool surface is very comprehensive, covering CRUD for most resources, replay, retries, anomaly management, and webhook setup. Minor gaps exist (no delete for destinations, no update for sources), but core workflows are well-supported.