Skip to main content
Glama

3GPP Scout

by com.3gppscout
OverviewDiscussionsAdmin

Search Combined Search Combined Post

search_combined_search_combined_post
Read-only

Search specification text and figures together. Use when a question may be answered by a diagram or a clause.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language search query. Searches both text and images simultaneously.
rerankNoRerank text results for better precision. Always leave true.
deduplicateNoCollapse near-duplicate text and image results from different releases/versions; collapsed matches appear in each winner's 'also_in' with release, version, and scores. Ignored when filter_release is set.
rerank_top_kNoNumber of text results after reranking. Use 3–5 for focused lookups, 10–20 for research.
filter_seriesNoRestrict by series: '38' = NR/5G, '23' = system architecture, '36' = LTE, '33' = security.
filter_releaseNoRestrict to a specific 3GPP release. Examples: 'Rel-15', 'Rel-17', 'Rel-20'. Omit for all indexed releases (Rel-15 through Rel-20).
filter_doc_typeNoRestrict by document type: 'TS' (Technical Specification) or 'TR' (Technical Report).
available_beforeNoOnly versions uploaded to the 3GPP archive before this date (YYYY-MM-DD; before 00:00 UTC, so the day itself is excluded), e.g. a patent application's priority date. A version whose upload time is unknown is left out. Usually one version per release of each spec is indexed (the newest in that release, Rel-15 onward), so a release appears only if that version predates the cutoff; older versions are in the 3GPP archive but not searchable here.
text_match_countNoText candidates before reranking. Default 30 balances speed and quality.
filter_doc_numberNoRestrict to a specific document, e.g. '38.331', '23.501'. Numeric format only.
image_match_countNoNumber of image/diagram results to return alongside text results.
include_section_textNoInclude full parent section text for each text chunk.
text_match_thresholdNoText similarity threshold. Leave at 0 (default) and rely on reranking.
filter_section_numberNoRestrict to a section, e.g. '5.3.5'. Only useful with filter_doc_number.
image_match_thresholdNoImage similarity threshold. Default 0 returns best matches.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
rerankedYes
text_totalYes
image_totalYes
text_resultsYes
image_resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / elapsed_ms
      Removed value: -{
-  "title": "Elapsed Ms",
-  "type": "number"
-}
    • changedOutput schema / required
      Previous value: -[
-  "query",
-  "text_results",
-  "image_results",
-  "text_total",
-  "image_total",
-  "reranked",
-  "elapsed_ms"
-]New value: +[
+  "query",
+  "text_results",
+  "image_results",
+  "text_total",
+  "image_total",
+  "reranked"
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / text_results / items / properties / children
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "properties": {
+          "section_number": {
+            "title": "Section Number",
+            "type": "string"
+          },
+          "section_title": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "title": "Section Title"
+          },
+          "token_count": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "title": "Token Count"
+          }
+        },
+        "required": [
+          "section_number"
+        ],
+        "title": "SectionChild",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "With include_children: the section's sub-clauses, without text.",
+  "title": "Children"
+}
    • addedOutput schema / properties / text_results / items / properties / descendant_count
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "With include_children: sub-clauses at any depth.",
+  "title": "Descendant Count"
+}
  3. Changed5 schema fields changed
    • addedInput schema / properties / available_before
      Added value: +{
+  "anyOf": [
+    {
+      "format": "date",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Only versions uploaded to the 3GPP archive before this date (YYYY-MM-DD; before 00:00 UTC, so the day itself is excluded), e.g. a patent application's priority date. A version whose upload time is unknown is left out. Usually one version per release of each spec is indexed (the newest in that release, Rel-15 onward), so a release appears only if that version predates the cutoff; older versions are in the 3GPP archive but not searchable here.",
+  "title": "Available Before"
+}
    • changedOutput schema / properties / image_results / items / properties / also_in / anyOf
      Previous value: -[
-  {
-    "items": {
-      "description": "Reference to another release/version that matched the same section.",
-      "properties": {
-        "release": {
-          "title": "Release",
-          "type": "string"
-        },
-        "relevance_score": {
-          "anyOf": [
-            {
-              "type": "number"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Relevance Score"
-        },
-        "similarity": {
-          "anyOf": [
-            {
-              "type": "number"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Similarity"
-        },
-        "version": {
-          "title": "Version",
-          "type": "string"
-        }
-      },
-      "required": [
-        "release",
-        "version"
-      ],
-      "title": "AlsoIn",
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "description": "Reference to another release/version that matched the same section.",
+      "properties": {
+        "archive_uploaded_at": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "When this version was uploaded to the 3GPP archive (ISO 8601, UTC); null when unknown.",
+          "title": "Archive Uploaded At"
+        },
+        "release": {
+          "title": "Release",
+          "type": "string"
+        },
+        "relevance_score": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "title": "Relevance Score"
+        },
+        "similarity": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "title": "Similarity"
+        },
+        "version": {
+          "title": "Version",
+          "type": "string"
+        }
+      },
+      "required": [
+        "release",
+        "version"
+      ],
+      "title": "AlsoIn",
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedOutput schema / properties / image_results / items / properties / provenance
      Added value: +{
+  "anyOf": [
+    {
+      "description": "When this spec version reached the public 3GPP archive, and the TSG plenary it came from.\n\nEvery value comes from the 3GPP FTP server: archive and dated plenary folder listings, 3GPP's lists of\nspecifications arising from each TSG round, and the 3GPP change request database. Unknown values stay null.",
+      "properties": {
+        "archive_date_source": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "'ftp_archive_listing' (the spec's folder under /ftp/Specs/archive/) or 'ftp_plenary_folder_listing' (a dated plenary folder that showed an earlier time).",
+          "title": "Archive Date Source"
+        },
+        "archive_uploaded_at": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "When this version's zip was uploaded to the 3GPP archive (ISO 8601, UTC), as the 3GPP FTP folder listing at archive_url shows it. If 3GPP re-uploaded the file, the earliest time seen. Null when not found; see unknown_reasons.",
+          "title": "Archive Uploaded At"
+        },
+        "archive_url": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The zip on the 3GPP FTP server whose folder listing gives archive_uploaded_at; open its folder to verify the time.",
+          "title": "Archive Url"
+        },
+        "notes": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Anything a reviewer should know, e.g. the file was re-uploaded or two sources name different meetings.",
+          "title": "Notes"
+        },
+        "plenary_batch": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "YYYY-MM of the plenary round whose batch of specifications includes this version (3GPP's dated folders, /ftp/Specs/YYYY-MM/).",
+          "title": "Plenary Batch"
+        },
+        "plenary_batch_source": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "'tsg_spec_list' (stated in 3GPP's list of specifications arising from that TSG round), 'tsg_meeting_start' (the month the plenary in tsg_meeting started) or 'ftp_plenary_folder' (the earliest dated folder holding the zip).",
+          "title": "Plenary Batch Source"
+        },
+        "statement": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The known facts as plain sentences, ready to quote, e.g. 'Uploaded to the 3GPP archive on 2026-09-24 at 16:47 UTC. Approved at TSG SA #113 (2026-09-15 to 2026-09-18).' It says 'uploaded to the 3GPP archive' and 'approved at', never 'published': no source states a publication date.",
+          "title": "Statement"
+        },
+        "tsg_meeting": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Plenary meeting ID: 'SP-113' (TSG SA #113), 'RP-109' (TSG RAN), 'CP-110' (TSG CT); a trailing '-e' marks an electronic meeting.",
+          "title": "Tsg Meeting"
+        },
+        "tsg_meeting_end": {
+          "anyOf": [
+            {
+              "format": "date",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Last day of the plenary meeting.",
+          "title": "Tsg Meeting End"
+        },
+        "tsg_meeting_name": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The meeting as 3GPP names it, e.g. 'TSG SA #113'.",
+          "title": "Tsg Meeting Name"
+        },
+        "tsg_meeting_relation": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "'approved': change requests approved at this meeting created this version (3GPP CR database). 'arising_from': 3GPP lists this version among the specifications arising from this meeting. 'presented': a draft (below version 3.0.0) presented to this meeting.",
+          "title": "Tsg Meeting Relation"
+        },
+        "tsg_meeting_source": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "'cr_database' (3GPP change request database export) or 'tsg_spec_list' (3GPP's list of specifications arising from that TSG round).",
+          "title": "Tsg Meeting Source"
+        },
+        "tsg_meeting_source_url": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The 3GPP file that names the meeting.",
+          "title": "Tsg Meeting Source Url"
+        },
+        "tsg_meeting_start": {
+          "anyOf": [
+            {
+              "format": "date",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "First day of the plenary meeting.",
+          "title": "Tsg Meeting Start"
+        },
+        "unknown_reasons": {
+          "anyOf": [
+            {
+              "additionalProperties": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Why a field is null, by field name. archive_uploaded_at: 'not_in_archive_listing'. tsg_meeting: 'before_tsg_lists_no_approved_cr' (uploaded before March 2023, when 3GPP's per-round spec lists start, and created by no approved change request, e.g. a release upgrade), 'draft_not_listed', or 'not_in_cr_database_or_tsg_lists'. Nothing is guessed.",
+          "title": "Unknown Reasons"
+        }
+      },
+      "title": "SpecProvenance",
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "When this version was uploaded to the 3GPP archive and the TSG plenary it came from, with sources. Null when the version has no provenance row yet."
+}
    • changedOutput schema / properties / text_results / items / properties / also_in / anyOf
      Previous value: -[
-  {
-    "items": {
-      "description": "Reference to another release/version that matched the same section.",
-      "properties": {
-        "release": {
-          "title": "Release",
-          "type": "string"
-        },
-        "relevance_score": {
-          "anyOf": [
-            {
-              "type": "number"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Relevance Score"
-        },
-        "similarity": {
-          "anyOf": [
-            {
-              "type": "number"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Similarity"
-        },
-        "version": {
-          "title": "Version",
-          "type": "string"
-        }
-      },
-      "required": [
-        "release",
-        "version"
-      ],
-      "title": "AlsoIn",
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "description": "Reference to another release/version that matched the same section.",
+      "properties": {
+        "archive_uploaded_at": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "When this version was uploaded to the 3GPP archive (ISO 8601, UTC); null when unknown.",
+          "title": "Archive Uploaded At"
+        },
+        "release": {
+          "title": "Release",
+          "type": "string"
+        },
+        "relevance_score": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "title": "Relevance Score"
+        },
+        "similarity": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "title": "Similarity"
+        },
+        "version": {
+          "title": "Version",
+          "type": "string"
+        }
+      },
+      "required": [
+        "release",
+        "version"
+      ],
+      "title": "AlsoIn",
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedOutput schema / properties / text_results / items / properties / provenance
      Added value: +{
+  "anyOf": [
+    {
+      "description": "When this spec version reached the public 3GPP archive, and the TSG plenary it came from.\n\nEvery value comes from the 3GPP FTP server: archive and dated plenary folder listings, 3GPP's lists of\nspecifications arising from each TSG round, and the 3GPP change request database. Unknown values stay null.",
+      "properties": {
+        "archive_date_source": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "'ftp_archive_listing' (the spec's folder under /ftp/Specs/archive/) or 'ftp_plenary_folder_listing' (a dated plenary folder that showed an earlier time).",
+          "title": "Archive Date Source"
+        },
+        "archive_uploaded_at": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "When this version's zip was uploaded to the 3GPP archive (ISO 8601, UTC), as the 3GPP FTP folder listing at archive_url shows it. If 3GPP re-uploaded the file, the earliest time seen. Null when not found; see unknown_reasons.",
+          "title": "Archive Uploaded At"
+        },
+        "archive_url": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The zip on the 3GPP FTP server whose folder listing gives archive_uploaded_at; open its folder to verify the time.",
+          "title": "Archive Url"
+        },
+        "notes": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Anything a reviewer should know, e.g. the file was re-uploaded or two sources name different meetings.",
+          "title": "Notes"
+        },
+        "plenary_batch": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "YYYY-MM of the plenary round whose batch of specifications includes this version (3GPP's dated folders, /ftp/Specs/YYYY-MM/).",
+          "title": "Plenary Batch"
+        },
+        "plenary_batch_source": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "'tsg_spec_list' (stated in 3GPP's list of specifications arising from that TSG round), 'tsg_meeting_start' (the month the plenary in tsg_meeting started) or 'ftp_plenary_folder' (the earliest dated folder holding the zip).",
+          "title": "Plenary Batch Source"
+        },
+        "statement": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The known facts as plain sentences, ready to quote, e.g. 'Uploaded to the 3GPP archive on 2026-09-24 at 16:47 UTC. Approved at TSG SA #113 (2026-09-15 to 2026-09-18).' It says 'uploaded to the 3GPP archive' and 'approved at', never 'published': no source states a publication date.",
+          "title": "Statement"
+        },
+        "tsg_meeting": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Plenary meeting ID: 'SP-113' (TSG SA #113), 'RP-109' (TSG RAN), 'CP-110' (TSG CT); a trailing '-e' marks an electronic meeting.",
+          "title": "Tsg Meeting"
+        },
+        "tsg_meeting_end": {
+          "anyOf": [
+            {
+              "format": "date",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Last day of the plenary meeting.",
+          "title": "Tsg Meeting End"
+        },
+        "tsg_meeting_name": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The meeting as 3GPP names it, e.g. 'TSG SA #113'.",
+          "title": "Tsg Meeting Name"
+        },
+        "tsg_meeting_relation": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "'approved': change requests approved at this meeting created this version (3GPP CR database). 'arising_from': 3GPP lists this version among the specifications arising from this meeting. 'presented': a draft (below version 3.0.0) presented to this meeting.",
+          "title": "Tsg Meeting Relation"
+        },
+        "tsg_meeting_source": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "'cr_database' (3GPP change request database export) or 'tsg_spec_list' (3GPP's list of specifications arising from that TSG round).",
+          "title": "Tsg Meeting Source"
+        },
+        "tsg_meeting_source_url": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The 3GPP file that names the meeting.",
+          "title": "Tsg Meeting Source Url"
+        },
+        "tsg_meeting_start": {
+          "anyOf": [
+            {
+              "format": "date",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "First day of the plenary meeting.",
+          "title": "Tsg Meeting Start"
+        },
+        "unknown_reasons": {
+          "anyOf": [
+            {
+              "additionalProperties": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Why a field is null, by field name. archive_uploaded_at: 'not_in_archive_listing'. tsg_meeting: 'before_tsg_lists_no_approved_cr' (uploaded before March 2023, when 3GPP's per-round spec lists start, and created by no approved change request, e.g. a release upgrade), 'draft_not_listed', or 'not_in_cr_database_or_tsg_lists'. Nothing is guessed.",
+          "title": "Unknown Reasons"
+        }
+      },
+      "title": "SpecProvenance",
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "When this version was uploaded to the 3GPP archive and the TSG plenary it came from, with sources. Null when the version has no provenance row yet."
+}
  4. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context of its own — nothing about ranking, latency, result mixing, or cost of the combined search — so it clears the lower bar set by annotations but adds no extra value.

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?

Two short sentences, purpose first, usage condition second, with zero filler. Nothing can be trimmed without losing routing information.

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 15-parameter tool with an output schema and full schema-level documentation, the description's job is narrow: state what it searches and when to pick it over the text-only or image-only siblings. It does the first well and the second adequately, leaving only explicit sibling routing unaddressed.

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 every parameter carries a detailed inline description (rerank, deduplicate, available_before semantics, match counts). The description adds no parameter guidance, so the baseline of 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?

States a specific verb+resource and a clear scope: 'Search specification text and figures together.' The word 'together' distinguishes it from the sibling text-only and image-only search tools, though it does not name them explicitly.

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?

'Use when a question may be answered by a diagram or a clause' gives a concrete triggering condition that separates this from a plain text search. It stops short of naming the alternatives (search_text_search_text_post, search_images_search_images_post) or stating when to prefer them.

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

All 3GPP Scout toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources