Skip to main content
Glama

List SAP Cloud ALM data

calm_list
Read-only

List or query SAP Cloud ALM collections such as tasks, projects, features, documents, and test cases with filters, paging, field selection, exact counts, and grouped breakdowns.

Instructions

List or query any SAP Cloud ALM collection (tasks, projects, features, documents, test cases, hierarchy nodes, cross-library objects, landscape objects, status events, code lists). Choose a "resource"; OData resources accept filter/select/expand/orderby, every resource pages with top/skip; REST resources read only the params calm_resources lists for them, and any other param (including $filter) is rejected rather than ignored. Defects: resource="tasks", task_type="CALMDEF". To answer "how many?" pass count_only=true, or group_by="status" for a breakdown — never list records to count them, as a few hundred tasks overflow most clients. See calm_resources for the full catalog.

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>"
    },
    "name": "calm_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoFetch specific tasks by id (resource:tasks); sent as a comma-separated list
topNoMaximum number of records (page size)
skipNoRecords to skip (page offset)
tagsNoTag filters (resource:tasks)
expandNoOData $expand — comma-separated navigation properties
fieldsNoComma-separated field projection applied by calmcp to the returned records (any resource). Use it to keep responses small, e.g. "displayId,title,status,assigneeName,timeboxId". Unlike $select this works for REST resources too. Unknown names are rejected
filterNoOData $filter, e.g. "status eq 'CIPDFCTOPEN'". OData resources only: REST resources have no server-side filter and reject it. calm_resources lists the parameters each resource reads
selectNoOData $select — comma-separated field list
statusNoStatus code filter (e.g. CIPDFCTOPEN; or deployment plan status)
orderbyNoOData $orderby, e.g. "priority desc". OData resources, and REST resources whose calm_resources entry lists orderby; any other resource rejects it
task_idNoTask id (required for task sub-resources)
team_idNoTeam id (required for team_roles/program_team_roles)
group_byNoComma-separated field name(s) to break the count down by, e.g. "status" or "projectName,status". Returns {total, groups:[{value,count}]} instead of records. Also the quickest way to discover which values a field actually takes
resourceYesWhich collection to list (see calm_resources for the catalog and required params)
task_typeNoTask type filter (resource:tasks). CALMDEF = Defect
count_onlyNoReturn ONLY the total number of matching records, no records at all. Use this for every "how many ...?" question — the answer is a few hundred bytes instead of hundreds of KB. Works for every resource and provider
program_idNoProgram id (required for program_teams)
project_idNoProject id (required for tasks/deliverables/etc.)
sub_statusNoSub-status code filter (resource:tasks)
timebox_idNoTimebox (sprint/phase) id filter (resource:tasks). Applied by calmcp after fetching, paging through the project automatically
with_countNoReturn the total as "@count" ALONGSIDE the records (OData resources and analytics only). For a total without the records, use count_only instead
assignee_idNoAssignee id filter (resource:tasks)
group_limitNoMaximum groups returned by group_by (default 50); the rest fold into otherCount
project_nameNoProject name instead of project_id, e.g. "S4 Transformation" (case and spacing ignored, otherwise exact). Works wherever project_id does; an ambiguous or unknown name is an error naming the candidates
rest_filtersNoQuery parameters of the REST resources that take them (landscape_objects, landscape_access_control_lists, bsm_events); not OData, see filter for that
timebox_nameNoTimebox name filter, e.g. "Sprint 5" (resource:tasks). Resolved against the project's timeboxes; errors listing the known names when it does not match
last_changed_dateNoLast-changed date filter (resource:tasks). Prefix with an operator: gt:, eq: or lt:, e.g. "gt:2026-08-01"
solution_process_idNoSolution process id filter (resource:task_solution_process_assignments)
last_changed_timestampNoLast-changed timestamp filter (resource:tasks). Prefix with gt:, eq: or lt: and use ISO 8601, e.g. "gt:2026-08-01T00:00:00Z". Use this for incremental "what changed since" queries

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.0.0
    • removedInput schema / properties / count
      Removed value: -{
      -  "description": "Return the total as \"@count\" ALONGSIDE the records (OData resources and analytics only). For a total without the records, use count_only instead",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / filters
      Removed value: -{
      -  "additionalProperties": {
      -    "type": "string"
      -  },
      -  "description": "Free-form REST filters for landscape_objects / bsm_events",
      -  "propertyNames": {
      -    "type": "string"
      -  },
      -  "type": "object"
      -}
    • removedInput schema / properties / limit
      Removed value: -{
      -  "description": "REST page size (REST resources)",
      -  "exclusiveMinimum": 0,
      -  "maximum": 9007199254740991,
      -  "type": "integer"
      -}
    • removedInput schema / properties / offset
      Removed value: -{
      -  "description": "REST page offset (REST resources)",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / properties / resource / enum
      Previous value: -[
      -  "features",
      -  "feature_external_references",
      -  "feature_url_references",
      -  "feature_task_assignments",
      -  "feature_priorities",
      -  "feature_statuses",
      -  "documents",
      -  "document_types",
      -  "document_statuses",
      -  "document_sources",
      -  "document_priorities",
      -  "document_approval_states",
      -  "hierarchy_nodes",
      -  "manual_test_cases",
      -  "automated_test_cases",
      -  "test_activities",
      -  "test_actions",
      -  "xlib_applications",
      -  "xlib_configurations",
      -  "xlib_developments",
      -  "xlib_interfaces",
      -  "xlib_application_url_references",
      -  "xlib_configuration_url_references",
      -  "xlib_development_url_references",
      -  "xlib_interface_url_references",
      -  "xlib_configuration_activities",
      -  "xlib_configuration_activity_types",
      -  "xlib_configuration_assignments",
      -  "xlib_application_priorities",
      -  "xlib_application_readiness",
      -  "xlib_application_usage_statuses",
      -  "xlib_application_clean_core_levels",
      -  "xlib_application_upgrade_impacts",
      -  "xlib_configuration_priorities",
      -  "xlib_configuration_readiness",
      -  "xlib_development_priorities",
      -  "xlib_development_readiness",
      -  "xlib_development_usage_statuses",
      -  "xlib_development_clean_core_levels",
      -  "xlib_development_upgrade_impacts",
      -  "xlib_interface_priorities",
      -  "xlib_interface_readiness",
      -  "xlib_interface_usage_statuses",
      -  "xlib_interface_clean_core_levels",
      -  "xlib_interface_upgrade_impacts",
      -  "scopes",
      -  "solution_scenario_versions",
      -  "scope_solution_processes",
      -  "business_processes",
      -  "solution_processes",
      -  "solution_process_flows",
      -  "solution_activities",
      -  "process_assets",
      -  "test_plans",
      -  "test_case_assignments",
      -  "test_plan_tag_assignments",
      -  "tasks",
      -  "task_solution_process_assignments",
      -  "task_subtasks",
      -  "task_comments",
      -  "task_references",
      -  "task_relations",
      -  "task_feature_assignments",
      -  "task_document_assignments",
      -  "task_hierarchy_assignments",
      -  "deliverables",
      -  "workstreams",
      -  "projects",
      -  "project_timeboxes",
      -  "project_teams",
      -  "team_roles",
      -  "programs",
      -  "program_teams",
      -  "program_team_roles",
      -  "system_groups",
      -  "deployment_plans",
      -  "landscape_objects",
      -  "landscape_access_control_lists",
      -  "bsm_events"
      -]New value: +[
      +  "features",
      +  "feature_external_references",
      +  "feature_url_references",
      +  "feature_task_assignments",
      +  "feature_transports",
      +  "feature_transport_references",
      +  "feature_priorities",
      +  "feature_statuses",
      +  "documents",
      +  "document_types",
      +  "document_statuses",
      +  "document_sources",
      +  "document_priorities",
      +  "document_approval_states",
      +  "hierarchy_nodes",
      +  "manual_test_cases",
      +  "automated_test_cases",
      +  "test_activities",
      +  "test_actions",
      +  "xlib_applications",
      +  "xlib_configurations",
      +  "xlib_developments",
      +  "xlib_interfaces",
      +  "xlib_application_url_references",
      +  "xlib_configuration_url_references",
      +  "xlib_development_url_references",
      +  "xlib_interface_url_references",
      +  "xlib_configuration_activities",
      +  "xlib_configuration_activity_types",
      +  "xlib_configuration_assignments",
      +  "xlib_application_priorities",
      +  "xlib_application_readiness",
      +  "xlib_application_usage_statuses",
      +  "xlib_application_clean_core_levels",
      +  "xlib_application_upgrade_impacts",
      +  "xlib_configuration_priorities",
      +  "xlib_configuration_readiness",
      +  "xlib_development_priorities",
      +  "xlib_development_readiness",
      +  "xlib_development_usage_statuses",
      +  "xlib_development_clean_core_levels",
      +  "xlib_development_upgrade_impacts",
      +  "xlib_interface_priorities",
      +  "xlib_interface_readiness",
      +  "xlib_interface_usage_statuses",
      +  "xlib_interface_clean_core_levels",
      +  "xlib_interface_upgrade_impacts",
      +  "scopes",
      +  "solution_scenario_versions",
      +  "scope_solution_processes",
      +  "business_processes",
      +  "solution_processes",
      +  "solution_process_flows",
      +  "solution_activities",
      +  "process_assets",
      +  "test_plans",
      +  "test_case_assignments",
      +  "test_plan_tag_assignments",
      +  "tasks",
      +  "task_solution_process_assignments",
      +  "task_subtasks",
      +  "task_comments",
      +  "task_references",
      +  "task_relations",
      +  "task_feature_assignments",
      +  "task_document_assignments",
      +  "task_hierarchy_assignments",
      +  "deliverables",
      +  "workstreams",
      +  "projects",
      +  "project_timeboxes",
      +  "project_teams",
      +  "team_roles",
      +  "programs",
      +  "program_teams",
      +  "program_team_roles",
      +  "system_groups",
      +  "deployment_plans",
      +  "landscape_objects",
      +  "landscape_access_control_lists",
      +  "bsm_events"
      +]
    • addedInput schema / properties / rest_filters
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "description": "Query parameters of the REST resources that take them (landscape_objects, landscape_access_control_lists, bsm_events); not OData, see filter for that",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • changedInput schema / properties / skip / description
      Previous value: -"OData $skip — records to skip"New value: +"Records to skip (page offset)"
    • changedInput schema / properties / top / description
      Previous value: -"OData $top — maximum number of records"New value: +"Maximum number of records (page size)"
    • addedInput schema / properties / with_count
      Added value: +{
      +  "description": "Return the total as \"@count\" ALONGSIDE the records (OData resources and analytics only). For a total without the records, use count_only instead",
      +  "type": "boolean"
      +}
  2. Changed9 schema fields changedv0.9.4
    • addedInput schema / properties / program_id / minLength
      Added value: +1
    • removedInput schema / properties / program_id / pattern
      Removed value: -"^(?!\\.\\.?$).+$"
    • addedInput schema / properties / project_id / minLength
      Added value: +1
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^(?!\\.\\.?$).+$"
    • addedInput schema / properties / project_name
      Added value: +{
      +  "description": "Project name instead of project_id, e.g. \"S4 Transformation\" (case and spacing ignored, otherwise exact). Works wherever project_id does; an ambiguous or unknown name is an error naming the candidates",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / task_id / minLength
      Added value: +1
    • removedInput schema / properties / task_id / pattern
      Removed value: -"^(?!\\.\\.?$).+$"
    • addedInput schema / properties / team_id / minLength
      Added value: +1
    • removedInput schema / properties / team_id / pattern
      Removed value: -"^(?!\\.\\.?$).+$"
  3. Changed6 schema fields changedv0.9.2
    • addedInput schema / properties / filters / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / group_limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / skip / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / top / maximum
      Added value: +9007199254740991
  4. Changed4 schema fields changedv0.9.1
    • addedInput schema / properties / program_id / pattern
      Added value: +"^(?!\\.\\.?$).+$"
    • addedInput schema / properties / project_id / pattern
      Added value: +"^(?!\\.\\.?$).+$"
    • addedInput schema / properties / task_id / pattern
      Added value: +"^(?!\\.\\.?$).+$"
    • addedInput schema / properties / team_id / pattern
      Added value: +"^(?!\\.\\.?$).+$"
  5. Changed7 schema fields changedv0.9.0
    • addedInput schema / properties / count
      Added value: +{
      +  "description": "Return the total as \"@count\" ALONGSIDE the records (OData resources and analytics only). For a total without the records, use count_only instead",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / count_only
      Added value: +{
      +  "description": "Return ONLY the total number of matching records, no records at all. Use this for every \"how many ...?\" question — the answer is a few hundred bytes instead of hundreds of KB. Works for every resource and provider",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / filter / description
      Previous value: -"OData $filter, e.g. \"status eq 'CIPDFCTOPEN'\""New value: +"OData $filter, e.g. \"status eq 'CIPDFCTOPEN'\". OData resources only: REST resources have no server-side filter and reject it. calm_resources lists the parameters each resource reads"
    • addedInput schema / properties / group_by
      Added value: +{
      +  "description": "Comma-separated field name(s) to break the count down by, e.g. \"status\" or \"projectName,status\". Returns {total, groups:[{value,count}]} instead of records. Also the quickest way to discover which values a field actually takes",
      +  "type": "string"
      +}
    • addedInput schema / properties / group_limit
      Added value: +{
      +  "description": "Maximum groups returned by group_by (default 50); the rest fold into otherCount",
      +  "exclusiveMinimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / orderby / description
      Previous value: -"OData $orderby, e.g. \"priority desc\" (OData resources / analytics only)"New value: +"OData $orderby, e.g. \"priority desc\". OData resources, and REST resources whose calm_resources entry lists orderby; any other resource rejects it"
    • changedInput schema / properties / resource / enum
      Previous value: -[
      -  "features",
      -  "feature_external_references",
      -  "feature_url_references",
      -  "feature_task_assignments",
      -  "feature_priorities",
      -  "feature_statuses",
      -  "documents",
      -  "document_types",
      -  "document_statuses",
      -  "document_sources",
      -  "document_priorities",
      -  "document_approval_states",
      -  "hierarchy_nodes",
      -  "manual_test_cases",
      -  "automated_test_cases",
      -  "test_activities",
      -  "test_actions",
      -  "xlib_applications",
      -  "xlib_configurations",
      -  "xlib_developments",
      -  "xlib_interfaces",
      -  "xlib_application_url_references",
      -  "xlib_configuration_url_references",
      -  "xlib_development_url_references",
      -  "xlib_interface_url_references",
      -  "xlib_configuration_activities",
      -  "xlib_configuration_activity_types",
      -  "xlib_configuration_assignments",
      -  "scopes",
      -  "solution_scenario_versions",
      -  "scope_solution_processes",
      -  "business_processes",
      -  "solution_processes",
      -  "solution_process_flows",
      -  "solution_activities",
      -  "process_assets",
      -  "test_plans",
      -  "test_case_assignments",
      -  "test_plan_tag_assignments",
      -  "tasks",
      -  "task_solution_process_assignments",
      -  "task_subtasks",
      -  "task_comments",
      -  "task_references",
      -  "task_relations",
      -  "task_feature_assignments",
      -  "task_document_assignments",
      -  "task_hierarchy_assignments",
      -  "deliverables",
      -  "workstreams",
      -  "projects",
      -  "project_timeboxes",
      -  "project_teams",
      -  "team_roles",
      -  "programs",
      -  "program_teams",
      -  "program_team_roles",
      -  "system_groups",
      -  "deployment_plans",
      -  "landscape_objects",
      -  "bsm_events"
      -]New value: +[
      +  "features",
      +  "feature_external_references",
      +  "feature_url_references",
      +  "feature_task_assignments",
      +  "feature_priorities",
      +  "feature_statuses",
      +  "documents",
      +  "document_types",
      +  "document_statuses",
      +  "document_sources",
      +  "document_priorities",
      +  "document_approval_states",
      +  "hierarchy_nodes",
      +  "manual_test_cases",
      +  "automated_test_cases",
      +  "test_activities",
      +  "test_actions",
      +  "xlib_applications",
      +  "xlib_configurations",
      +  "xlib_developments",
      +  "xlib_interfaces",
      +  "xlib_application_url_references",
      +  "xlib_configuration_url_references",
      +  "xlib_development_url_references",
      +  "xlib_interface_url_references",
      +  "xlib_configuration_activities",
      +  "xlib_configuration_activity_types",
      +  "xlib_configuration_assignments",
      +  "xlib_application_priorities",
      +  "xlib_application_readiness",
      +  "xlib_application_usage_statuses",
      +  "xlib_application_clean_core_levels",
      +  "xlib_application_upgrade_impacts",
      +  "xlib_configuration_priorities",
      +  "xlib_configuration_readiness",
      +  "xlib_development_priorities",
      +  "xlib_development_readiness",
      +  "xlib_development_usage_statuses",
      +  "xlib_development_clean_core_levels",
      +  "xlib_development_upgrade_impacts",
      +  "xlib_interface_priorities",
      +  "xlib_interface_readiness",
      +  "xlib_interface_usage_statuses",
      +  "xlib_interface_clean_core_levels",
      +  "xlib_interface_upgrade_impacts",
      +  "scopes",
      +  "solution_scenario_versions",
      +  "scope_solution_processes",
      +  "business_processes",
      +  "solution_processes",
      +  "solution_process_flows",
      +  "solution_activities",
      +  "process_assets",
      +  "test_plans",
      +  "test_case_assignments",
      +  "test_plan_tag_assignments",
      +  "tasks",
      +  "task_solution_process_assignments",
      +  "task_subtasks",
      +  "task_comments",
      +  "task_references",
      +  "task_relations",
      +  "task_feature_assignments",
      +  "task_document_assignments",
      +  "task_hierarchy_assignments",
      +  "deliverables",
      +  "workstreams",
      +  "projects",
      +  "project_timeboxes",
      +  "project_teams",
      +  "team_roles",
      +  "programs",
      +  "program_teams",
      +  "program_team_roles",
      +  "system_groups",
      +  "deployment_plans",
      +  "landscape_objects",
      +  "landscape_access_control_lists",
      +  "bsm_events"
      +]
  6. Changed10 schema fields changedv0.2.0
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Comma-separated field projection applied by calmcp to the returned records (any resource). Use it to keep responses small, e.g. \"displayId,title,status,assigneeName,timeboxId\". Unlike $select this works for REST resources too. Unknown names are rejected",
      +  "type": "string"
      +}
    • addedInput schema / properties / ids
      Added value: +{
      +  "description": "Fetch specific tasks by id (resource:tasks); sent as a comma-separated list",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / last_changed_date
      Added value: +{
      +  "description": "Last-changed date filter (resource:tasks). Prefix with an operator: gt:, eq: or lt:, e.g. \"gt:2026-08-01\"",
      +  "type": "string"
      +}
    • addedInput schema / properties / last_changed_timestamp
      Added value: +{
      +  "description": "Last-changed timestamp filter (resource:tasks). Prefix with gt:, eq: or lt: and use ISO 8601, e.g. \"gt:2026-08-01T00:00:00Z\". Use this for incremental \"what changed since\" queries",
      +  "type": "string"
      +}
    • addedInput schema / properties / program_id
      Added value: +{
      +  "description": "Program id (required for program_teams)",
      +  "type": "string"
      +}
    • changedInput schema / properties / resource / enum
      Previous value: -[
      -  "features",
      -  "feature_external_references",
      -  "feature_url_references",
      -  "feature_task_assignments",
      -  "feature_priorities",
      -  "feature_statuses",
      -  "documents",
      -  "document_types",
      -  "document_statuses",
      -  "document_sources",
      -  "document_priorities",
      -  "document_approval_states",
      -  "hierarchy_nodes",
      -  "manual_test_cases",
      -  "automated_test_cases",
      -  "test_activities",
      -  "test_actions",
      -  "xlib_applications",
      -  "xlib_configurations",
      -  "xlib_developments",
      -  "xlib_interfaces",
      -  "tasks",
      -  "task_subtasks",
      -  "task_comments",
      -  "task_references",
      -  "task_relations",
      -  "task_feature_assignments",
      -  "task_document_assignments",
      -  "task_hierarchy_assignments",
      -  "deliverables",
      -  "workstreams",
      -  "projects",
      -  "project_timeboxes",
      -  "project_teams",
      -  "team_roles",
      -  "programs",
      -  "system_groups",
      -  "deployment_plans",
      -  "landscape_objects",
      -  "bsm_events"
      -]New value: +[
      +  "features",
      +  "feature_external_references",
      +  "feature_url_references",
      +  "feature_task_assignments",
      +  "feature_priorities",
      +  "feature_statuses",
      +  "documents",
      +  "document_types",
      +  "document_statuses",
      +  "document_sources",
      +  "document_priorities",
      +  "document_approval_states",
      +  "hierarchy_nodes",
      +  "manual_test_cases",
      +  "automated_test_cases",
      +  "test_activities",
      +  "test_actions",
      +  "xlib_applications",
      +  "xlib_configurations",
      +  "xlib_developments",
      +  "xlib_interfaces",
      +  "xlib_application_url_references",
      +  "xlib_configuration_url_references",
      +  "xlib_development_url_references",
      +  "xlib_interface_url_references",
      +  "xlib_configuration_activities",
      +  "xlib_configuration_activity_types",
      +  "xlib_configuration_assignments",
      +  "scopes",
      +  "solution_scenario_versions",
      +  "scope_solution_processes",
      +  "business_processes",
      +  "solution_processes",
      +  "solution_process_flows",
      +  "solution_activities",
      +  "process_assets",
      +  "test_plans",
      +  "test_case_assignments",
      +  "test_plan_tag_assignments",
      +  "tasks",
      +  "task_solution_process_assignments",
      +  "task_subtasks",
      +  "task_comments",
      +  "task_references",
      +  "task_relations",
      +  "task_feature_assignments",
      +  "task_document_assignments",
      +  "task_hierarchy_assignments",
      +  "deliverables",
      +  "workstreams",
      +  "projects",
      +  "project_timeboxes",
      +  "project_teams",
      +  "team_roles",
      +  "programs",
      +  "program_teams",
      +  "program_team_roles",
      +  "system_groups",
      +  "deployment_plans",
      +  "landscape_objects",
      +  "bsm_events"
      +]
    • addedInput schema / properties / solution_process_id
      Added value: +{
      +  "description": "Solution process id filter (resource:task_solution_process_assignments)",
      +  "type": "string"
      +}
    • changedInput schema / properties / team_id / description
      Previous value: -"Team id (required for team_roles)"New value: +"Team id (required for team_roles/program_team_roles)"
    • addedInput schema / properties / timebox_id
      Added value: +{
      +  "description": "Timebox (sprint/phase) id filter (resource:tasks). Applied by calmcp after fetching, paging through the project automatically",
      +  "type": "string"
      +}
    • addedInput schema / properties / timebox_name
      Added value: +{
      +  "description": "Timebox name filter, e.g. \"Sprint 5\" (resource:tasks). Resolved against the project's timeboxes; errors listing the known names when it does not match",
      +  "type": "string"
      +}
  7. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Despite annotations already covering the safety profile (readOnlyHint/openWorldHint), the description adds real behavioral detail: REST resources reject unsupported params rather than silently ignoring them, both providers page with top/skip, only OData resources accept filter, and large result sets overflow clients. It also discloses the shape change with group_by ({total, groups}) and the point of count_only (bytes vs hundreds of KB).

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?

Purpose is front-loaded and the remaining clauses are dense but all load-bearing (OData vs REST rules, paging, count/group shortcuts, pointer to calm_resources). It runs long as continuous prose, which makes individual rules harder to scan than they need to be, but nothing is filler.

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

Completeness5/5

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

For a 29-parameter, multi-provider tool with no output schema, the description covers the decisions an agent must make: which resource, which filtering dialect, how to page, how to count or group, and where the authoritative per-resource parameter list lives. The group_by payload shape is spelled out, which is the one return contract an agent needs up front.

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 coverage is 100%, so the schema already carries the per-parameter explanations; the description's contribution is guidance-level (count_only for counts, group_by for value discovery, task_type=CALMDEF for defects) rather than adding meaning the schema lacks. That is additive but modest against a fully documented 29-param schema, so the baseline applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (list/query) and a precisely scoped resource (any SAP Cloud ALM collection), immediately enumerating the collection families so an agent knows the breadth without opening the enum. The scope line makes it implicitly distinct from calm_get (single record) and calm_analytics, and it points at calm_resources for the catalog.

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?

Gives concrete routing rules — use count_only for "how many?", group_by for breakdowns, never list-then-count, see calm_resources for per-resource params — plus a worked example (Defects via resource=tasks, task_type=CALMDEF). It does not explicitly contrast with calm_get or calm_analytics, so sibling selection is left partly implicit.

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