Skip to main content
Glama
SepineTam

Stata-MCP

by SepineTam
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

read_log

Read Stata log files (.log or .smcl) to review command output. Use full, core, or dict formats, or limit to first/last N lines for targeted inspection.

Instructions

Read a Stata log file (.log or .smcl) and return its content. Supports full, core, and dict output formats. Use lines to return only the first/last N lines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesNo
encodingNoutf-8
file_pathYes
output_formatNocore

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.21.0
    • removedInput schema / properties / is_beta
      Removed value: -{
-  "default": false,
-  "title": "Is Beta",
-  "type": "boolean"
-}
    • changedInput schema / properties / output_format / default
      Previous value: -"dict"New value: +"core"
  2. Changed8 schema fields changedv1.16.2
    • addedInput schema / properties / encoding
      Added value: +{
+  "default": "utf-8",
+  "title": "Encoding",
+  "type": "string"
+}
    • addedInput schema / properties / file_path
      Added value: +{
+  "title": "File Path",
+  "type": "string"
+}
    • addedInput schema / properties / is_beta
      Added value: +{
+  "default": false,
+  "title": "Is Beta",
+  "type": "boolean"
+}
    • addedInput schema / properties / lines
      Added value: +{
+  "default": 0,
+  "title": "Lines",
+  "type": "integer"
+}
    • removedInput schema / properties / log_path
      Removed value: -{
-  "title": "Log Path",
-  "type": "string"
-}
    • addedInput schema / properties / output_format
      Added value: +{
+  "default": "dict",
+  "enum": [
+    "full",
+    "core",
+    "dict"
+  ],
+  "title": "Output Format",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "log_path"
-]New value: +[
+  "file_path"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "read_logOutput",
+  "type": "object"
+}
  3. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It does not explicitly state that the operation is read-only or describe any side effects, authentication needs, or constraints. However, the read nature is implied.

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?

Three sentences, all informative, no wasted words. Front-loads purpose and adds details about formats and the lines parameter efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters, no annotations, and presence of output schema, the description covers the basics but leaves gaps in parameter meaning (encoding, file_path) and does not fully compensate for missing schema descriptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must explain parameters. It describes output_format enum values and lines parameter but does not clarify encoding or file_path. The lines behavior (positive/negative for first/last) is ambiguous.

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 clearly states it reads Stata log files (.log or .smcl) and returns content, with verb 'Read' and resource 'log file'. It distinguishes from siblings (get_data_info, help, stata_do) by specifying the file type and output formats.

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?

Provides basic guidance on output formats and lines parameter, but does not explicitly state when to use the tool vs. alternatives, nor when not to use it. Usage context is implied but not formalized.

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/SepineTam/mcp-for-stata'

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