Skip to main content
Glama

search

Search 3GPP specifications using FTS5 syntax. Narrow results with AND/OR/NOT, phrases, prefixes, column filters, or spec IDs, and paginate through matches.

Instructions

Full-text search across 3GPP specifications using SQLite FTS5 syntax.

Query syntax:

  • AND/OR/NOT: AMF AND authentication

  • Phrase: "service based interface"

  • Prefix: handov*

  • Column filter: title:authentication or content:handover

  • Proximity: NEAR(AMF UE, 5)

  • Hyphenated or dotted terms (e.g. IMS-AKA, sec-agree, 38.101) are auto-quoted to avoid FTS5 syntax errors.

  • After a positive term, "-term" excludes that term (e.g. AMF -SMF), same as NOT. An exclusion cannot begin a query or immediately follow AND/OR.

Stemming:

  • The index uses porter stemming: inflected English forms match each other (handover finds handovers).

  • Prefix and phrase queries operate on stemmed forms, so they can match a bit more broadly than the exact surface text.

Pagination:

  • Results come as {results, total_count, limit, offset}; total_count is the full match count.

  • Use limit (default 10, max 200) and offset to page through matches beyond the first page.

Tips:

  • Use exact 3GPP terms (AMF, SMF, gNB, UE, NRF, PCF, etc.)

  • Phrase search improves precision for multi-word concepts

  • title:term restricts matches to section headings only

  • Use spec_ids to search across multiple specifications at once

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results per page (default: 10, max: 200)
queryYesrequired,FTS5 query string. Hyphenated or dotted terms like IMS-AKA and 38.101 are auto-quoted. Use AND/OR/NOT operators and double-quoted phrases for exact matches (e.g. '"core network" AND AMF').
offsetNoNumber of results to skip for pagination (default: 0). Combine with total_count in the response to page through all matches.
spec_idNoLimit search to a single specification (e.g. TS 23.501). Ignored when spec_ids is provided.
spec_idsNoLimit search to one or more specifications (e.g. ["TS 23.501", "TS 23.502"]). Takes precedence over spec_id.
Behavior4/5

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

Given there are no annotations, the description carries full burden for behavioral disclosure. It explicitly states key behaviors: auto-quoting of hyphenated/dotted terms, exclusion syntax, porter stemming, pagination with total_count, and the precedence of spec_ids over spec_id. This is comprehensive beyond what the schema reveals.

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?

The description is structured with clear sections (Query syntax, Stemming, Pagination, Tips) and is well organized. It earns its length given the complexity of FTS5 syntax, but could be slightly more concise in the exclusion rules section, which repeats some details from the syntax list.

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?

The description covers query syntax, stemming, pagination, and provides domain tips. There is no output schema, but the response structure is described inline (results, total_count, limit, offset). The description is complete for a search tool of this complexity. Minor gap: it does not explain what happens on an empty query or FTS5 syntax errors beyond auto-quoting.

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 baseline is 3. The description does add value for some parameters (e.g., explaining spec_ids precedence over spec_id, and specifying default/max for limit), but mostly the query syntax details are an extension of the 'query' parameter's natural behavior rather than new parameter-specific semantics. The description does not add meaning significantly beyond the schema.

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?

The description begins with a clear verb and resource: 'Full-text search across 3GPP specifications'. It specifies the technology (SQLite FTS5 syntax), and the query examples clearly differentiate it from sibling tools like search_openapi or list_specs. The purpose is specific and distinct.

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?

The description provides extensive query syntax and tips for effective search (tips on exact terms, phrase search, column filters), but it does not explicitly state when to use this tool versus alternatives like search_openapi or get_section. There is no 'when-not-to-use' guidance. Usage is implied through examples and tips but not formally defined.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/higebu/3gpp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server