Skip to main content
Glama
Sign In
mcp-abap-adt

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetObjectNodeFromCache

Retrieves a cached object node by object type, object name, and technical name, and expands its URI when available.

Instructions

[read-only] Returns a node from the in-memory objects list cache by OBJECT_TYPE, OBJECT_NAME, TECH_NAME, and expands OBJECT_URI if present. Runs outside batch mode.

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": {
      "object_type": "<object_type>",
      "object_name": "<object_name>",
      "tech_name": "<tech_name>"
    },
    "name": "GetObjectNodeFromCache"
  }
}

Input Schema

NameRequiredDescriptionDefault
tech_nameYes[read-only] Technical name
object_nameYes[read-only] Object name
object_typeYes[read-only] Object type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does add useful traits — read-only, cache-backed, expands OBJECT_URI when present, and only valid outside batch mode. However it omits what happens on a cache miss (error vs. null), whether the cache can be stale, and what the returned node looks like.

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?

Two compact sentences with the read-only marker and the lookup key set front-loaded. No filler, only the trailing batch-mode note is slightly tacked on.

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

Completeness3/5

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

For a cache-read tool with no output schema and no annotations, the description should explain return shape and cache-miss behavior. It covers the lookup basis and the OBJECT_URI expansion but leaves those gaps.

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 all three parameters are already documented; the description only restates the key names in caps. The one added semantic, OBJECT_URI expansion, concerns the return value rather than input parameters.

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?

States a specific verb and resource ('Returns a node from the in-memory objects list cache') plus the exact key set used for lookup. It is distinguishable from siblings like GetObjectsList or GetObjectsByType, though the description never explicitly contrasts with them.

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?

'Runs outside batch mode' implies a usage context, but the agent is left to infer when to prefer this over GetObjectsList/GetObjectsByType. No explicit when-to-use or when-not-to-use guidance is given.

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