Skip to main content
Glama
nerdit-ai

Nerdit

Official
by nerdit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

project_logs

Read bounded logs for one service in an explicit project. Filter by source, timestamp, substring, and tail size to inspect build or runtime output.

Instructions

Read bounded logs of one service resolved within an explicit project.

Prefer the immutable project ID returned by list_projects. Membership is
resolved by the daemon; a same-name replacement cannot inherit a retired ID.
Existing node grants and local token roles still apply.

Input Schema

NameRequiredDescriptionDefault
grepNoLiteral substring filter; never a regex.
tailNoNewest matching lines; clamped to [1, 1000].
sinceNoInclusive ISO-8601 timestamp filter.
sourceNoLog stream: all, build or runtime.all
projectYesImmutable prj_ ID or name of an existing project. Prefer the ID from list_projects: a retired ID never addresses a same-name replacement.
serviceNoService inside the project; omit for web.web
since_idNoExclusive log cursor; ignored while tail is sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that membership is resolved by the daemon, retired IDs never address same-name replacements, and existing grants/token roles apply. It does not cover return format, pagination behavior, or other operational details, leaving clear gaps.

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 front-loaded with the core action and is only three sentences long. It avoids repetition and keeps the important project-ID guidance visible, though the final sentence about grants and token roles could be integrated more tightly.

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 seven-parameter log-reading tool with complete schema coverage but no annotations or output schema, the description covers purpose, project resolution, and auth context. It is largely sufficient for correct invocation, though it could say more about the returned log data or filtering behavior.

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 schema already documents all seven parameters. The description reinforces the project ID preference but adds little semantic meaning beyond what the schema already states, making the baseline 3 appropriate.

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?

The description states a specific verb and resource: "Read bounded logs of one service resolved within an explicit project." This is clear enough for an agent to understand the core operation. It does not explicitly distinguish itself from the sibling tool service_logs, so it falls short of 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?

The description offers guidance to prefer the immutable project ID returned by list_projects and notes that node grants and local token roles still apply. However, it does not explicitly say when to use this tool versus alternatives such as service_logs, nor does it state when not to use it.

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

Deploy Server

Other Tools