Skip to main content
Glama

Search Classes

search_classes
Read-only

Find SAP IS-U and FI-CA classes by name or description keywords, returning matching results with relevance scores.

Instructions

Search for SAP classes by name or description. Use this when the user asks things like:

  • 'What class handles installations?'

  • 'Find classes for IS-U contracts'

  • 'Which class works with devices?'

  • 'Show me FI-CA classes'

The catalog contains IS-U and FI-CA classes. Returns matching classes with relevance scores.

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": {
      "query": "<query>"
    },
    "name": "search_classes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (default 10, max 50)
queryYesSearch query - can be a class name (e.g., 'CL_ISU_CONTRACT'), partial name (e.g., 'CL_ISU_'), or description keywords (e.g., 'installation', 'contract', 'device')

Output Schema

NameRequiredDescriptionDefault
hintNoGuidance when no results
queryYesThe search query used
resultsYesMatching classes
successNo
total_resultsYesNumber of results found
total_in_catalogYesTotal classes in catalog

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: the lookup is scoped to an IS-U and FI-CA class catalog, and results come back with relevance scores. It says nothing about pagination, empty-result behavior, or matching rules, so it adds value without being rich.

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 and domain scope are front-loaded in the first sentence, with examples and return behavior following in a logical order. The four bullets overlap somewhat (all illustrate name-or-keyword lookup) and could be trimmed to two without losing signal, but nothing is misleading or wasted wholesale.

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 two-parameter read-only search with a fully documented schema and a published output schema, the description covers what the tool searches, over what domain, and roughly what it returns. Only edge-case behavior (no matches, result caps, ranking semantics) is left implicit, which is minor at this complexity.

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% and the schema already explains that the query accepts a full class name, a partial name like 'CL_ISU_', or description keywords, plus the limit default and max. The description's example queries reinforce this but contribute no syntax or semantics the schema lacks, so the baseline 3 applies.

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 opens with a specific verb+resource: 'Search for SAP classes by name or description'. The second sentence names the catalog contents ('IS-U and FI-CA classes'), which implicitly separates it from the other search_* siblings (function modules, tables, transactions). It stops short of explicitly contrasting with those siblings, so a 4 rather than a 5.

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?

Four concrete example user utterances ('What class handles installations?', 'Show me FI-CA classes') give the agent a reliable trigger pattern, which is stronger than generic 'use when searching' language. It does not state when NOT to use it or point to a named alternative such as search_function_modules, so it falls below the top band.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.