Skip to main content
Glama

Search Tables

search_tables
Read-only

Search SAP tables by name, description, or field name to find where data such as material master or MATNR is stored. Returns matching tables with relevance scores.

Instructions

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

  • 'What table stores material master data?'

  • 'Which table has the MATNR field?'

  • 'Find tables related to purchase orders'

Returns matching tables 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_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (default 10, max 50)
queryYesSearch query - can be a table name (e.g., 'MARA'), partial name (e.g., 'MAR'), description keywords (e.g., 'material master'), or field name (e.g., 'MATNR')
include_fieldsNoAlso search within field names and descriptions

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 only that results carry relevance scores, and since an output schema exists the response shape is already documented, so incremental behavioral disclosure is thin.

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?

Front-loaded with the core action and resource before the example list. The three example queries arguably restate the same searchable dimensions twice, but they are compact and genuinely helpful for query formulation.

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?

With an output schema handling return values, full schema parameter coverage, and annotations covering safety, the remaining burden on the description is purpose and query formulation, both of which are addressed. Minor gaps like matching semantics (exact vs partial) are not mentioned but are partially implied by the schema examples.

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 every parameter is documented in the schema itself, including examples for query and the limit cap. The description adds no additional parameter meaning beyond the schema, making the baseline 3 appropriate.

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 and resource ('Search for SAP tables') and enumerates the searchable dimensions (name, description, field), which cleanly separates it from siblings like search_classes and search_transactions by resource type.

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 three concrete example user questions that map directly onto the tool, which is stronger guidance than a generic 'use when searching'. It does not name an alternative tool or state when not to use it, so it stops short of full routing guidance.

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