Skip to main content
Glama

route_to_journal

Automatically route journal entries to the correct project's database. Specify a project ID explicitly or let it auto-detect from context to log entries under the right project.

Instructions

Route a piece of text to the correct project's journal database.

Returns the project the entry was routed to, the journal entry ID, and storage location.

USE WHEN: the user wants to log something and you want it filed under the right project automatically. NOT FOR: identifying the project without writing — use identify_project. ALTERNATIVES: passing project_id explicitly to skip auto-detection.

BEHAVIOR: SIDE EFFECT — writes a row to the per-project journal SQLite database. Idempotent only if you pass the same content + project pair. Auto-detects the project via identify_project + get_active_project blend when project_id is omitted.

PARAMETERS: text: journal entry content. Required, non-empty. project_id: explicit project slug to route to. Omit to auto-detect.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
project_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses side effect (writes to SQLite database), idempotency condition (same content+project pair), and auto-detection behavior. No annotations provided, so description fully compensates.

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?

Well-structured with labeled sections, but slightly verbose. Every sentence adds value, but could be slightly more concise.

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

Completeness5/5

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

Comprehensive for the tool's complexity: covers usage, behavior, parameters, and references output schema. No gaps for an agent to invoke correctly.

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

Parameters5/5

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

Adds meaning beyond schema: describes text as 'Required, non-empty' and project_id as 'explicit project slug... Omit to auto-detect.' Schema coverage is 0%, so this is essential.

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?

Clearly states the tool routes text to a project's journal database, specifies return values (project, journal entry ID, storage location), and distinguishes from siblings via 'ALTERNATIVES' mentioning identify_project.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Provides explicit 'USE WHEN', 'NOT FOR', and 'ALTERNATIVES' sections, giving clear guidance on when to use this tool vs alternatives like identify_project.

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/ContextPulse/contextpulse'

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