3GPP Scout

Get Sections Sections Get

get_sections_sections_get

Read-only

Read the text of specific sections of a specification, in short excerpts.

Input Schema

TableJSON Schema

Name	Required	Description
`latest`	No	If true, return one version only: the given version, else the newest version of the given release, else the newest indexed version. Each result then has latest_version and latest_release; an older result also has same_text_as_latest, whether the newest version's same section has the same text (null when the newest version lacks it).
`prefix`	No	If true, also list sub-sections. E.g. '5.3' returns 5.3 with text plus 5.3.1, 5.3.1.1, 5.3.2, etc. as numbers and titles only (API and MCP return one clause of text per call). Also works for annex prefixes: 'A' with prefix=true lists A, A.1, A.2.3, etc.
`release`	No	3GPP release, e.g. 'Rel-19'. Omit to return all indexed versions of the document.
`version`	No	Specific document version, e.g. '19.1.0'. Usually not needed — use release instead.
`doc_number`	Yes	Document number, e.g. '38.331' (NR RRC), '23.501' (system architecture), '38.300' (NR overview). Required — section numbers like '5.1' exist in hundreds of unrelated documents. Use the numeric format without the 'TS'/'TR' prefix.
`section_number`	Yes	Section number to look up. Numeric ('5.3.5', '6.3.2'), trailing-letter ('5.3.1a'), or 3GPP annex ('A.1', 'B.2.3') identifiers are all supported. Use the same dot-delimited numbering as it appears in the spec; case-sensitive (annex letters are uppercase).
`available_before`	No	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. With latest=true and no version, returns the newest version uploaded before the date.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

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. With latest=true and no version, returns the newest version uploaded before the date.",
+  "title": "Available Before"
+}

addedOutput schema / properties / result / 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."
+}

First observedOct 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds a genuinely useful behavioral fact not in structured data: results are returned as 'short excerpts', warning the agent that the full clause text may be truncated and that another call or tool may be needed for complete text.

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?

A single front-loaded sentence with no filler; the scope constraint ('specific sections') and the output-shape caveat ('short excerpts') are both delivered immediately.

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 present, return-value detail is not required, annotations cover safety, and all 7 parameters are documented in the schema. The one remaining gap is that it does not route the agent to get_sections_batch for multi-section retrieval, which would be a natural exclusion to state.

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 parameter docs are unusually rich (version inheritance, prefix sub-section behavior, available_before date semantics), so the schema carries the burden. The description adds no parameter-level information beyond it, which matches the baseline 3.

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 (Read) and resource (text of specific sections of a specification), which clearly separates it from document-level siblings like get_document_documents or list_sections_sections_toc_get. It stops short of naming the closely related get_sections_batch, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the resource: look up the text of a named section. There is no explicit statement of when to prefer this over get_sections_batch (multiple sections), list_sections_sections_toc_get (titles only), or the search tools, so the agent must infer the routing.

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

All 3GPP Scout tools Inspect

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.