Skip to main content
Glama

Get one SAP Cloud ALM entity

calm_get
Read-only

Fetch a single SAP Cloud ALM entity by resource and ID; select fields to reduce response size for large records.

Instructions

Fetch a single SAP Cloud ALM entity by id (a feature can also be fetched by display id like "6-123"). Choose a "resource" and pass its "id". See calm_resources for valid ones. A task has ~70 fields: pass fields="displayId,title,status,..." to keep the answer small.

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": {
      "resource": "<resource>",
      "id": "<id>"
    },
    "name": "calm_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEntity id (uuid, REST id, or feature display id like "6-123")
expandNoOData $expand for OData entities; REST entities reject it
fieldsNoComma-separated fields to keep, e.g. "displayId,title,status". Use it for large entities such as tasks; an unknown name is rejected with the available ones
resourceYesWhich single entity to fetch (see calm_resources)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.4
    • addedInput schema / properties / id / minLength
      Added value: +1
    • removedInput schema / properties / id / pattern
      Removed value: -"^(?!\\.\\.?$).+$"
  2. Changed2 schema fields changedv0.9.1
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Comma-separated fields to keep, e.g. \"displayId,title,status\". Use it for large entities such as tasks; an unknown name is rejected with the available ones",
      +  "type": "string"
      +}
    • addedInput schema / properties / id / pattern
      Added value: +"^(?!\\.\\.?$).+$"
  3. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / expand / description
      Previous value: -"OData $expand for OData entities"New value: +"OData $expand for OData entities; REST entities reject it"
  4. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / resource / enum
      Previous value: -[
      -  "feature",
      -  "document",
      -  "hierarchy_node",
      -  "manual_test_case",
      -  "automated_test_case",
      -  "xlib_application",
      -  "xlib_configuration",
      -  "xlib_development",
      -  "xlib_interface",
      -  "task",
      -  "deliverable",
      -  "project",
      -  "program",
      -  "timebox",
      -  "team",
      -  "deployment_plan",
      -  "system_group"
      -]New value: +[
      +  "feature",
      +  "document",
      +  "hierarchy_node",
      +  "manual_test_case",
      +  "automated_test_case",
      +  "xlib_application",
      +  "xlib_configuration",
      +  "xlib_development",
      +  "xlib_interface",
      +  "task",
      +  "deliverable",
      +  "project",
      +  "program",
      +  "timebox",
      +  "team",
      +  "deployment_plan",
      +  "system_group",
      +  "program_team",
      +  "scope",
      +  "solution_scenario_version",
      +  "business_process",
      +  "solution_process",
      +  "solution_activity",
      +  "process_asset",
      +  "test_plan",
      +  "test_case_assignment"
      +]
  5. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that a feature can be fetched by display id and that tasks have ~70 fields, making fields= important for keeping responses small.

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

Conciseness5/5

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

The description is front-loaded with the core action and scope, then adds only practical details about resource selection and field projection. It is appropriately sized with no wasted sentences.

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?

For a read-only entity fetch with a rich 100%-covered schema and annotations, the description covers the essential retrieval model, display-id exception, and large-entity field tip. Minor gaps remain around expand behavior and response shape, but no output schema exists to require return-value documentation.

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 the schema already documents resource, id, fields, and expand. The description reinforces the id and fields usage but largely repeats schema content and does not add information about the expand parameter.

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 and resource: 'Fetch a single SAP Cloud ALM entity by id.' The word 'single' and the id-based retrieval imply the distinction from list-style siblings, but the description does not explicitly name calm_list or another alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the retrieval pattern: choose a resource and pass its id, and it points to calm_resources for valid resources. It also gives concrete field-projection advice for large task entities, though it does not explicitly state when to prefer calm_list or another sibling.

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