Scribase

logs.tail

Read-onlyIdempotent

Tail the environment's most-recent log lines, newest first. GET .../logs. level is debug, info, warn, or error. from is an opaque pagination cursor.

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": {
      "organization_id": "<organization_id>",
      "project_id": "<project_id>",
      "environment_id": "<environment_id>"
    },
    "name": "logs.tail"
  }
}

Input Schema

Name	Required	Description
`from`	No	Opaque pagination cursor from a previous response
`level`	No	Filter: debug, info, warn, or error
`limit`	No	Maximum lines (default 200, max 1000)
`project_id`	Yes	project_id (required)
`environment_id`	Yes	environment_id (required)
`organization_id`	Yes	organization_id (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the newest-first ordering, which materially affects how a paginating agent consumes results, but says nothing about return line shape, rate limits, or what happens when no lines exist. The 'GET .../logs' fragment conveys little behavioral value.

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?

Three short sentences with the core purpose front-loaded and no padding. The 'GET .../logs' fragment is the only sentence that does not earn its place, being neither a full endpoint spec nor useful behavior.

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?

For a read-only listing tool with a fully documented schema, most of what an agent needs is present, but there is no output schema, so the description should say what a log line contains or how many fields to expect. It also omits default/max limit behavior, which lives only in the schema and matters for a tail operation.

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 baseline is 3. The description restates the level values and that 'from' is an opaque cursor — the same information already in the schema — and adds no extra meaning such as cursor direction or how 'from' interacts with newest-first ordering.

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 and resource ('Tail the environment's most-recent log lines') plus ordering ('newest first'), which is enough to distinguish it conceptually from logs.get or functions.logs. However, it never names those siblings to make the distinction explicit.

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?

'Tail' and 'most-recent' imply a use case (watching live/recent activity), but there is no explicit statement of when to choose this over logs.get or functions.logs, and no note about when this tool is inappropriate (e.g., historical search).

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

All Scribase 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.

Resources

Need Help?